Modified items

All recently modified items, latest first.

zope.testrunner-4.2.0-1.lbn13.noarch: zope.testrunner uses buildout. To start, run python bootstrap.py. It will create a number of directories and the bin/buildout script. Next, run bin/buildout. It will create a test script for you. Now, run bin/test to run the zope.testrunner test suite.

zope.testing-4.1.1-1.lbn13.noarch: This package provides a number of testing frameworks. cleanup Provides a mixin class for cleaning up after tests that make global changes. formparser An HTML parser that extracts form information. Python 2 only This is intended to support functional tests that need to extract information from HTML forms returned by the publisher. See formparser.txt. loggingsupport Support for testing logging code If you want to test that your code generates proper log output, you can create and install a handler that collects output. loghandler Logging handler for tests that check logging output. module Lets a doctest pretend to be a Python module. See module.txt. renormalizing Regular expression pattern normalizing output checker. Useful for doctests. server Provides a simple HTTP server compatible with the zope.app.testing functional testing API. Lets you interactively play with the system under test. Helpful in debugging functional doctest failures. Python 2 only setupstack A simple framework for automating doctest set-up and tear-down. See setupstack.txt. wait A small utility for dealing with timing non-determinism See wait.txt.

zope.testbrowser-3.11.1-2.lbn13.noarch: Programmable browser for functional black-box tests

zope.tales-3.5.3-1.lbn13.noarch: Template Attribute Language - Expression Syntax See http://www.zope.org/Wikis/DevSite/Projects/ZPT/TALES%20Specification%201.3

zope.tal-3.5.2-2.lbn13.noarch: The Zope3 Template Attribute Languate (TAL) specifies the custom namespace and attributes which are used by the Zope Page Templates renderer to inject dynamic markup into a page. It also includes the Macro Expansion for TAL (METAL) macro language used in page assembly. The dynamic values themselves are specified using a companion language, TALES (see the 'zope.tales' package for more). See: http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL%20Specification%201.4

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.


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