Modified items

All recently modified items, latest first.

zope-z3c.autoinclude-0.3.8-1.lbn25.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-2.lbn25.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-tempstorage-4.0.1-1.lbn25.noarch: A storage implementation which uses RAM to persist objects, much like MappingStorage. Unlike MappingStorage, it needs not be packed to get rid of non-cyclic garbage and it does rudimentary conflict resolution. This is a ripoff of Jim’s Packless bsddb3 storage.

zope-jarn.checkinterval-1.0-3.lbn25.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-ZopeUndo-4.3-1.lbn25.noarch: This package is used to support the Prefix object that Zope 2 uses for the undo log. It is a separate package only to aid configuration management. This package is included in Zope 2. It can be used in a ZEO server to allow it to support Zope 2’s undo log , without pulling in all of Zope 2.

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

zope-ZODB3-3.11.0-3.lbn25.py37.noarch: The ZODB3 distribution is a “meta” distribution that requires projects: ZODB, persistent, BTrees and ZEO, which, in the past, were included in the ZODB 3 project. For more information on ZODB, persistent, BTrees, and ZEO, see the respective project pages in PyPI:

zope-ZODB3-3.11.0-3.lbn25.py37.noarch: The ZODB3 distribution is a “meta” distribution that requires projects: ZODB, persistent, BTrees and ZEO, which, in the past, were included in the ZODB 3 project. For more information on ZODB, persistent, BTrees, and ZEO, see the respective project pages in PyPI:

zope-ZODB3-3.11.0-3.lbn25.py37.noarch: The ZODB3 distribution is a “meta” distribution that requires projects: ZODB, persistent, BTrees and ZEO, which, in the past, were included in the ZODB 3 project. For more information on ZODB, persistent, BTrees, and ZEO, see the respective project pages in PyPI:

zope-ZConfig-3.3.0-1.lbn25.noarch: ZConfig is a configuration library intended for general use. It supports a hierarchical schema-driven configuration model that allows a schema to specify data conversion routines written in Python. ZConfig’s model is very different from the model supported by the ConfigParser module found in Python’s standard library, and is more suitable to configuration-intensive applications. ZConfig schema are written in an XML-based language and are able to “import” schema components provided by Python packages. Since components are able to bind to conversion functions provided by Python code in the package (or elsewhere), configuration objects can be arbitrarily complex, with values that have been verified against arbitrary constraints. This makes it easy for applications to separate configuration support from configuration loading even with configuration data being defined and consumed by a wide range of separate packages. ZConfig is licensed under the Zope Public License, version 2.1. See the file LICENSE.txt in the distribution for the full license text. Reference documentation is available in the doc/ directory.

zope-RestrictedPython-4.0a3-1.lbn25.noarch: RestrictedPython provides a restricted execution environment for Python, e.g. for running untrusted code.

zope-RelStorage-pgsql-3.0.1-1.lbn25.x86_64: PostgreSQL backend for RelStorage

zope-RelStorage-pgsql-3.0.1-1.lbn25.x86_64: PostgreSQL backend for RelStorage

zope-RelStorage-pgsql-1.6.0b3-1.lbn19.noarch: PostgreSQL backend for RelStorage


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