Modified items

All recently modified items, latest first.

zope.preference-3.8.0-2.lbn13.noarch: User Preferences Framework

zope.pluggableauth-1.2-2.lbn13.noarch: Pluggable Authentication Utility

zope.password-3.6.1-2.lbn13.noarch: Password encoding and checking utilities

zope.pagetemplate-3.6.3-2.lbn13.noarch: zope.pagetemplate

zope.modulealias-3.4.0-4.lbn13.noarch: Zope modulealias

zope.mkzeoinstance-3.9.5-2.lbn13.noarch: Make standalone ZEO database server instances

zope.minmax-1.1.2-4.lbn13.noarch: zope.minmax

zope.mimetype-1.3.1-2.lbn13.noarch: A simple package for working with MIME content types

zope.login-1.0.0-2.lbn13.noarch: Login helpers for zope.publisher / authentication.

zope.location-3.9.1-2.lbn13.noarch: In Zope3, location are special objects that has a structural location.

zope.lifecycleevent-3.6.2-2.lbn13.noarch: ================= Life-cycle events ================= In Zope 3, events are used by components to inform each other about relevant new objects and object modifications. To keep all subscribers up to date it is indispensable that the life cycle of an object is accompanied by various events. >>> from zope.event import notify >>> from zope.lifecycleevent import ObjectCreatedEvent, ObjectModifiedEvent >>> class Sample(object) : ... "Test class" >>> obj = Sample() >>> notify(ObjectCreatedEvent(obj)) >>> obj.modified = True >>> notify(ObjectModifiedEvent(obj)) Zope 3's Dublin Core Metadata for instance, rely on the bare ObjectCreatedEvent and ObjectModifiedEvent to record creation and modification times. Other event consumers like catalogs and caches may need more information to update themselves in an efficient manner. The necessary information can be provided as optional modification descriptions of the ObjectModifiedEvent. Some examples: >>> from zope.interface import Interface, Attribute, implements >>> class IFile(Interface): ... data = Attribute("Data") ... >>> class File(object): ... implements(IFile) ... >>> file = File() >>> file.data = "123" >>> notify(ObjectModifiedEvent(obj, IFile)) This says that we modified something via IFile. Note that an interface is an acceptable description. In fact, we might allow pretty much anything as a description and it depends on your needs what kind of descriptions you use. In the following we use an IAttributes description to describe in more detail which parts of an object where modified : >>> file.data = "456" >>> from zope.dublincore.interfaces import IZopeDublinCore >>> from zope.interface import directlyProvides >>> from zope.annotation.interfaces import IAttributeAnnotatable >>> directlyProvides(file, IAttributeAnnotatable) >>> IZopeDublinCore(file).title = u"New title" >>> IZopeDublinCore(file).title = u"New description" >>> from zope.lifecycleevent import Attributes >>> event = ObjectModifiedEvent( ... obj, ... Attributes(IFile, 'data'), ... Attributes(IZopeDublinCore, 'title', 'description'), ... ) >>> notify(event) This says we modified the file data and the DC title and description. ======= CHANGES ======= 3.5.2 (2009-05-17) ------------------ - ``IObjectMovedEvent``, ``IObjectAddedEvent``, ``IObjectRemovedEvent`` interfaces and ``ObjectMovedEvent``, ``ObjectAddedEvent`` and ``ObjectRemovedEvent`` classes copied here from zope.container (plus tests). The intent is to allow packages that rely on these interfaces or the event classes to rely on zope.lifecycleevent (which has few dependencies) instead of zope.container (which has many). 3.5.1 (2009-03-09) ------------------ - Remove deprecated code and thus remove dependency on zope.deferredimport. - Change package's mailing list address to zope-dev at zope.org, as zope3-dev at zope.org is now retired. - Update package's description and documentation. 3.5.0 (2009-01-31) ------------------ - Remove old module declarations from classes. - Use zope.container instead of zope.app.container. 3.4.0 (2007-09-01) ------------------ Initial release as an independent package

zope.kgs-1.2.0-2.lbn13.noarch: Known-Good-Set (KGS) Support

zope.keyreference-3.6.4-2.lbn13.noarch: zope.keyreference

zope.intid-3.7.2-2.lbn13.noarch: zope.intid

zope.interface-4.0.1-4.lbn13.x86_64: This package provides an implementation of "object interfaces" for Python. Interfaces are a mechanism for labeling objects as conforming to a given API or contract. So, this package can be considered as implementation of the Design By Contract methodology support in Python.

zope.index-3.6.4-1.lbn13.x86_64: Zope Cataloging and Indexing Framework Catalogs provide management of collections of related indexes with a basic search algorithm.

zope.i18nmessageid-3.5.3-1.lbn13.x86_64: To translate any text, we must be able to discover the source domain of the text. A source domain is an identifier that identifies a project that produces program source strings. Source strings occur as literals in python programs, text in templates, and some text in XML data. The project implies a source language and an application context. We can think of a source domain as a collection of messages and associated translation strings. We often need to create unicode strings that will be displayed by separate views. The view cannot translate the string without knowing its source domain. A string or unicode literal carries no domain information, therefore we use messages. Messages are unicode strings which carry a translation source domain and possibly a default translation. They are created by a message factory. The message factory is created by calling MessageFactory with the source domain. This package provides facilities for delaring such messages within program source text; translation of the messages is the responsiblitiy of the 'zope.i18n' package.

zope.i18n-3.8.0-2.lbn13.noarch: This package implements several APIs related to internationalization and localization. * Locale objects for all locales maintained by the ICU project. * Gettext-based message catalogs for message strings. * Locale discovery for Web-based requests.

zope.html-2.1.0-2.lbn13.noarch: HTML and XHTML Editing Support

zope.hookable-4.0.0-2.lbn13.x86_64: Hookable object support. Support the efficient creation of hookable objects, which are callable objects that are meant to be replaced by other callables, at least optionally. The idea is you create a function that does some default thing and make it hookable. Later, someone can modify what it does by calling its sethook method and changing its implementation. All users of the function, including those that imported it, will see the change.

« Previous 20 items Next 20 items » 1 ... 2334 2335 2336 2337 2338 2339 2340 ... 2421


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

Sections

Modified items