Modified items

All recently modified items, latest first.

zope.sqlalchemy-0.6.1-3.lbn13.noarch: The aim of this package is to unify the plethora of existing packages integrating SQLAlchemy with Zope's transaction management. As such it seeks only to provide a data manager and makes no attempt to define a zopeish way to configure engines. For WSGI applications, Zope style automatic transaction management is available with repoze.tm2, a part of Repoze BFG and Turbogears 2.

zope.size-3.4.1-5.lbn13.noarch: This package provides a definition of simple interface that allows to retrieve the size of the object for displaying and for sorting. The default adapter is also provided. It expects objects to have the getSize method that returns size in bytes, however, it won't crash if an object doesn't have one and will show size as not available instead.

zope.site-3.9.2-2.lbn13.noarch: Local registries for zope component architecture

zope.security-3.8.3-2.lbn13.x86_64: The Security framework provides a generic mechanism to implement security policies on Python objects. This introduction provides a tutorial of the framework explaining concepts, design, and going through sample usage from the perspective of a Python programmer using the framework outside of Zope.

zope.schema-4.2.2-1.lbn13.noarch: ============== Zope 3 Schemas ============== Introduction ------------ Schemas extend the notion of interfaces to detailed descriptions of Attributes (but not methods). Every schema is an interface and specifies the public fields of an object. A *field* roughly corresponds to an attribute of a python object. But a Field provides space for at least a title and a description. It can also constrain its value and provide a validation method. Besides you can optionally specify characteristics such as its value being read-only or not required. Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought about Formulator for Zope 3 and PropertySets while at the Zope 3 sprint at the Zope BBQ in Berlin. They realized that if you strip all view logic from forms then you have something similar to interfaces. And thus schemas were born.

zope.publisher-3.12.6-2.lbn13.noarch: zope.publisher allows you to publish Python objects on the web. It has support for plain HTTP/WebDAV clients, web browsers as well as XML-RPC and FTP clients. Input and output streams are represented by request and response objects which allow for easy client interaction from Python. The behaviour of the publisher is geared towards WSGI compatibility.

zope.ptresource-3.9.0-2.lbn13.noarch: Page template resource plugin for zope.browserresource

zope.proxy-devel-3.6.1-2.lbn13.x86_64: This package provides the support files which can be used to build applications using the Zope proxy infrastructure

zope.proxy-3.6.1-2.lbn13.x86_64: Proxies are special objects which serve as mostly-transparent wrappers around another object, intervening in the apparent behavior of the wrapped object only when necessary to apply the policy (e.g., access checking, location brokering, etc.) for which the proxy is responsible. Editorial note: Unfortunately, we don't have separate documentation for zope.proxy at this time. This is a shame because they are generically useful. We are publishing this release without documentation mainly because it is a dependency of other releases.


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