Modified items

All recently modified items, latest first.

zope-z3c.checkversions-0.4.1-3.lbn13.noarch: Find newer package versions on PyPI

zope-z3c.blobfile-0.1.5-4.lbn13.noarch: This package provides an implementation of zope.app.file.interfaces.IFile which uses the Blob support introduced in ZODB 3.8. It's main purpose is to provide an easy migration path for existing instances. For more advanced file implementations see zope.file and z3c.extfile. The standard implementation in zope.app.file uses chunk objects to break big files into manageable parts. These chunks flow the server caches whereas blobs are directly consumed by the publisher. The main difference between this blob implementation and the old zope.app.file implementation can be seen in a replacement of the chunk objects by Blobs.

zope-z3c.batching-1.1.0-5.lbn13.noarch: This module implements a simple batching mechanism that allows you to split a large sequence into smaller batches.

zope-z3c.autoinclude-0.3.5-1.lbn13.noarch: This package adds two new ZCML directives to automatically detect ZCML files to include: "includeDependencies" and "includePlugins". When you want to include a Zope-based package in your application, you have to repeat yourself in two places: you have to add the package itself (in a setup.py, buildout, etc) and you also have to include its ZCML with an include directive or a package-includes slug. Because you have to repeat yourself, you can easily make an error where you add a new package but forget to include its ZCML. z3c.autoinclude lets you circumvent this error-prone process with automatic detection and inclusion of ZCML files.

zope-wildcard.fixpersistentutilities-1.1b7-1.lbn13.noarch: Introduction This product was created to help you remove nasty local persistent utilities that won't go away and can destroy your instance when you try to remove a product that registered one. Features * remove adapters * remove subscribers * remove provided interfaces * remove provided interfaces across the entire site - useful for removing collective.flowplayer Just append '/@@fix-persistent-utilities' onto your plone site root or the root of zope(for gsm) and browse through all your registered utilities on your site and remove things at will. By default, the tools prevents you from removing certain registrations; however, you can enter "expert mode" and remove whatever you want. WARNING!!! You can really screw up things if you do this wrong so use with extreme care and backup your instance before you use it. I will not take responsibility if you misuse this tool... Advice Do not include this product as part of your normal set of products. Only install this product on debug zope clients. This product should allow you to remove things from products that are no longer installed on the system; although, if you experience problems removing things, make sure to add those eggs to the system again.

zope-pgsql-2.13.18-2.lbn13.x86_64: This package contains the PostgreSQL backend for Zope and necessary startups

zope-oracle-2.13.18-2.lbn13.x86_64: This package contains the Oracle backend for Zope and necessary startups

zope-mysql-2.13.18-2.lbn13.x86_64: This package contains the MySQL backend for Zope and necessary startups

zope-jarn.checkinterval-1.0-3.lbn13.noarch: $ checkinterval 1305 The number you see is the recommended check interval for this machine; put it into your zope.conf file: python-check-interval 1305 Now restart Zope and bask in the glow. Why care? The Python Library Reference on the topic of check interval: "This integer value determines how often the interpreter checks for periodic things such as thread switches and signal handlers. The default is 100, meaning the check is performed every 100 Python virtual instructions. Setting it to a larger value may increase performance for programs using threads." Now, the Zope application server is such a program, and it benefits greatly from setting the right check interval. If the value is too low, Zope threads are interrupted unnecessarily, causing a noticable performance hit on today's multi-cpu hardware. Where's the 50 coming from? The constant 50 in the formula was determined by benchmarks performed at Zope Corporation and has become part of the "Zope lore" (See e.g. this post by Matt Kromer). Going beyond pystone/50 produced no further benefits. The value may well be meaningless for applications other than Zope and platforms other than Intel. Background More on check intervals and the GIL from David Beazly. For those back from the Beazly talk: Zope uses long running threads and asyncore, making it (more) independent from OS scheduling issues. Still, the interruption argument holds.

zope-instance-2.13.15-3.lbn13.x86_64: Setup of zope unix account and empty Zope database primed for this user

zope-cmf.pt-1.0-1.lbn13.noarch: The cmf.pt package allows using the Chameleon template engine with the Zope 2 CMF.

zope-ZPublisherEventsBackport-1.1-3.lbn13.noarch: Backport publication events from Zope 2.12 ZPublisher to Zope 2.10


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.