Modified items

All recently modified items, latest first.

zope-MultiMapping-2.13.0-3.lbn19.armv6hl: Special MultiMapping objects used in Zope2.

zope-Missing-3.2-1.lbn25.x86_64: Missing provides special objects used in some Zope2 internals like the ZCatalog.

zope-Jinja2-2.9.5-1.lbn19.noarch: A small but fast and easy to use stand-alone template engine written in pure python.

zope-ExtensionClass-4.3.0-1.lbn25.x86_64: ExtensionClass and ExtensionClass-related packages ExtensionClass This package provides a metaclass that allows classes implemented in extension modules to be subclassed in Python. Unless you need ExtensionClasses for legacy applications (e.g. Zope 2), you probably want to use Python’s new-style classes (available since Python 2.2). C omputedAttribute This package provides a way to attach attributes to an ExtensionClass or instance that are computed by calling a callable. This works very much like property known from new-style classes, except that a ComputedAttribute can also be attached to an instance and that it honours ExtensionClass semantics (which is useful for retaining Acquisition wrappers, for example). MethodObject This package lets you attach additional “methods” to ExtensionClasses. These “methods” are actually implemented by subclassing the MethodObject.Method class and implementing the __call__ method there. Instances of those classes will be bound to the instances they’re attached to and will receive that instance object as a first parameter (after self).

zope-ExtensionClass-2.13.2-3.lbn19.armv6hl: Metaclass for subclassable extension types

zope-DateTime-4.2-1.lbn25.noarch: The DateTime package ==================== Encapsulation of date/time values. Function Timezones() -------------------- Returns the list of recognized timezone names: >>> from DateTime import Timezones >>> zones = set(Timezones()) Almost all of the standard pytz timezones are included, with the exception of some commonly-used but ambiguous abbreviations, where historical Zope usage conflicts with the name used by pytz: >>> import pytz >>> [x for x in pytz.all_timezones if x not in zones] ['CET', 'EET', 'EST', 'MET', 'MST', 'WET']

zope-Acquisition-devel-4.4.2-1.lbn19.x86_64: Acquisition is a mechanism that allows objects to obtain attributes from the containment hierarchy they're in.

zope-Acquisition-devel-2.13.8-3.lbn19.armv6hl: Acquisition is a mechanism that allows objects to obtain attributes from the containment hierarchy they're in.

zope-Acquisition-4.4.2-1.lbn25.x86_64: Acquisition provides a powerful way to dynamically share information between objects. Zope 2 uses acquisition for a number of its key features including security, object publishing, and DTML variable lookup. Acquisition also provides an elegant solution to the problem of circular references for many classes of problems. While acquisition is powerful, you should take care when using acquisition in your applications. The details can get complex, especially with the differences between acquiring from context and acquiring from containment.

zope-Acquisition-2.13.8-3.lbn19.armv6hl: Acquisition is a mechanism that allows objects to obtain attributes from the containment hierarchy they're in.

zope-AccessControl-3.0.14-1.lbn25.x86_64: AccessControl provides a general security framework for use in Zope2.

zope-2.13.29-2.lbn25.noarch: Zope is an application server framework that enables developers to quickly build web applications such as intranets, portals, and content management systems.

zope-2.13.22-3.lbn19.armv6hl: Zope is an application server framework that enables developers to quickly build web applications such as intranets, portals, and content management systems.

zettwerk.ui-2.0-1.lbn19.noarch: Introduction zettwerk.ui integrates jquery.ui's themeroller into Plone 4.1. Themeroller is a tool to dynamically customize the jquery.ui css classes. For details about jquery.ui theming and themeroller see http://jqueryui.com/themeroller/. See it in action: http://www.youtube.com/watch?v=p4_jU-5HUYA Usage With this add-on it is very easy to adapt the look and color scheme of your plone site. After installation, there is a new extension product listed in the plone controlpanel which is called "Zettwerk UI Themer". Use the themes tab to create new themes via themeroller or apply one of the example themes from the themeroller gallery. Note that themeroller is only working in firefox, but the existing themes can be used with all browsers.

zest.releaser-6.13.5-1.lbn25.noarch: zest.releaser is collection of command-line programs to help you automate the task of releasing a software project. It's particularly helpful with Python package projects, but it can also be used for non-Python projects. For example, it's used to tag buildouts - a project only needs a version.txt file to be used with zest.releaser. It will help you to automate: * Updating the version number. The version number can either be in setup.py or version.txt. For example, 0.3.dev0 (current) to 0.3 (release) to 0.4.dev0 (new development version). * Updating the history/changes file. It logs the release date on release and adds a new section for the upcoming changes (new development version). * Tagging the release. It creates a tag in your version control system named after the released version number. * Uploading a source release to PyPI. It will only do this if the package is already registered there (else it will ask, defaulting to 'no'); the Zest Releaser is careful not to publish your private projects! It can also check out the tag in a temporary directory in case you need to modify it.

zest.pocompile-1.3-2.lbn19.noarch: This package compiles po files. It contains a zest.releaser entry point and a stand-alone command line tool. Goal You want to release a package that has a locales dir (or locale, or something else as long as it has a LC_MESSAGES folder somewhere in it) with translations in .po files. You want to include the compiled .mo files in your release as well, but you do not want to keep those in a revision control system (like subversion) as they are binary and can be easily recreated. That is good. This package helps with that. Want .mo files? Add a MANIFEST.in file. When you use python setup.py sdist to create a source distribution, distutils (or setuptools or distribute or distutils2) knows which files it should include by looking at the information of the revision control system (RCS). This is why in the case of subversion you should use a checkout and not an export: you need the versioning information. (For other RCS or for subversion 1.7+ you currently need to install extra packages like setuptools-git.)


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