Modified items

All recently modified items, latest first.

python2-zope.schema-4.9.3-1.lbn25.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.

python2-zope.proxy-4.3.1-10.lbn25.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.

python2-zope.interface-5.1.0-1.lbn25.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.

python2-zope.i18nmessageid-4.3.1-1.lbn25.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.

python2-zope.exceptions-4.3-1.lbn25.noarch: zope.exceptions :target:

python2-zope.event-4.4-1.lbn25.noarch: The ``zope.event`` package provides a simple event system. It provides: - An event publishing system - A very simple event-dispatching system on which more sophisticated event dispatching systems can be built. For example, a type-based event dispatching system that builds on ``zope.event`` can be found in ``zope.component``

python2-zope.deprecation-4.4.0-11.lbn25.noarch: When we started working on Zope 3.1, we noticed that the hardest part of the development process was to ensure backward-compatibility and correctly mark deprecated modules, classes, functions, methods and properties. This package provides a simple function called 'deprecated(names, reason)' to deprecate the previously mentioned Python objects.

zope-testing-zodb-2.13.30-3.lbn25.noarch: Custom ZODB for Demo(memory) storage

zope-testing-2.13.30-3.lbn25.noarch: Zope testing framework

zope-emacs-2.13.30-3.lbn25.noarch: Emacs editing for zope page templates, dtml, and other Zope-specific file extensions.

python2-tempita-0.5.1-20.lbn25.noarch: Tempita is a small templating language for text substitution.

python2-nose-1.3.7-19.lbn25.py37.noarch: nose extends the test loading and running features of unit test, making it easier to write, find and run tests. By default, nose will run tests in files or directories under the current working directory whose names include "test" or "Test" at a word boundary (like "test_this" or "functional_test" or "TestClass" but not "libtest"). Test output is similar to that of unit test, but also includes captured stdout output from failing tests, for easy print-style debugging. These features, and many more, are customizable through the use of plugins. Plugins included with nose provide support for doctest, code coverage and profiling, flexible attribute-based test selection, output capture and more.

python2-meld3-1.0.2-3.lbn25.noarch: meld3 is an HTML/XML templating system for Python 2.5+ which keeps template markup and dynamic rendering logic separate from one another.

python2-webencodings-0.5.1-6.lbn25.py37.noarch: This is a Python implementation of the WHATWG Encoding standard.

python-gocept.munin-0.1-3.lbn25.noarch: This package provides base classes for defining Munin graphs and a main function to handle munin-typical symlinked scripts. Munin plugin scripts ==================== A single plugin file defines (multiple) graphs by subclassing the bases as mentioned in the next section. The main function uses the called script's filename to determine which of the defined graphs is relevant. Data for each graph is determined by retrieving a text file from a URL (with possibly given basic authentication data). The format for the data is plain/text wich each line having key/value pairs split by ':'. The values are expected to be floats. All graph bases expect two environment variables to be set: URL The URL at which to retrieve data from. Must include a '%s' which encodes the graph name. AUTH HTTP basic authentication information. Either empty or in the form of 'username:password'. The environment variables can be configured using munin's `plugin-conf.d` like this: The plugin is called `prefix_something_1`:: [prefix_*] env.URL http://foo:8900/myapp/munin?data=%s env.AUTH admin:admin Graph bases =========== The following base classes are currently defined: SimpleGraph A simple graph with a single value that is plotted as an absolute value. SimpleMultiGraph Multiple absolute values plotted on the same graph and scale. more bases will be added as needed. Main function ============= The main function handles munin-typical `type_option_index` symlink scripts by looking at the name from which the main script was called. Example script ============== Here's a sample script that you could symlink into the `plugins` directory:: from gocept.munin.client import SimpleGraph, main class people(SimpleGraph): name = key = 'people' title = 'How many people are there?' category = 'Office' main() [root@mistress gocept.munin-0.1]# cat README.txt ========================================== Utilities for writing munin client scripts ========================================== This package provides base classes for defining Munin graphs and a main function to handle munin-typical symlinked scripts. Munin plugin scripts ==================== A single plugin file defines (multiple) graphs by subclassing the bases as mentioned in the next section. The main function uses the called script's filename to determine which of the defined graphs is relevant. Data for each graph is determined by retrieving a text file from a URL (with possibly given basic authentication data). The format for the data is plain/text wich each line having key/value pairs split by ':'. The values are expected to be floats. All graph bases expect two environment variables to be set: URL The URL at which to retrieve data from. Must include a '%s' which encodes the graph name. AUTH HTTP basic authentication information. Either empty or in the form of 'username:password'. The environment variables can be configured using munin's `plugin-conf.d` like this: The plugin is called `prefix_something_1`:: [prefix_*] env.URL http://foo:8900/myapp/munin?data=%s env.AUTH admin:admin Graph bases =========== The following base classes are currently defined: SimpleGraph A simple graph with a single value that is plotted as an absolute value. SimpleMultiGraph Multiple absolute values plotted on the same graph and scale. more bases will be added as needed. Main function ============= The main function handles munin-typical `type_option_index` symlink scripts by looking at the name from which the main script was called. Example script ============== Here's a sample script that you could symlink into the `plugins` directory:: from gocept.munin.client import SimpleGraph, main class people(SimpleGraph): name = key = 'people' title = 'How many people are there?' category = 'Office' main()

python-gocept.country-2.0-1.lbn25.noarch: This package lets you use the pycountry database within Zope 3. In practice, this means e.g., that you can easily get a zope.schema.Choice field to provide a full list of iso 3166 country codes. For more information about the database please refer to the pycountry product. gocept.country gocept.country provides Zope 3 sources for the pycountry databases. You can use it e.g. to get a zope.schema.Choice field with all iso 3166 countries. >>> import gocept.country >>> import gocept.country.db >>> import zope.schema ISO 3166 Countries To get a list of ISO 3166 countries in a webform, you can use the zope.schema.Choice field and provide the gocept.country.countries as source: >>> countries_field = zope.schema.Choice(title=u'Country', ... source=gocept.country.countries) >>> countries_field <zope.schema._field.Choice object at 0x...> >>> countries = iter(countries_field.source) The gocept.country.countries sourcefactory returns Country objects as values, which use the values from pycountry: >>> afghanistan = countries.next() >>> afghanistan <gocept.country.db.Country object at 0x...> >>> afghanistan.name u'Afghanistan' Calling the next() method again returns the next country from the source: >>> islands = countries.next() >>> islands.name u'\xc5land Islands' There are all information available, which you can get from pycountry: >>> afghanistan.alpha2 'AF' >>> afghanistan.alpha3 'AFG' >>> afghanistan.numeric '004' >>> afghanistan.official_name 'Islamic Republic of Afghanistan' To smaller the amount of results you can provide a list or tuple of countries you like to have in your source: >>> countries = iter(gocept.country.CountrySource(alpha2=['DE', 'US'])) >>> countries.next().name u'Germany' >>> countries.next().name u'United States' >>> countries.next().name Traceback (most recent call last): ... StopIteration Please note, that the result items are sorted by alpha2 code. Please also note, that you can provide alpha3 and numeric codes and names resp. official_names to smaller the amount of result items, too: >>> len(list(gocept.country.CountrySource())) 246 >>> len(list(gocept.country.CountrySource(alpha2=['DE', 'US', 'GB']))) 3 >>> len(list(gocept.country.CountrySource(alpha3=['DEU', 'USA']))) 2 >>> len(list(gocept.country.CountrySource(numeric=['276', ]))) 1 >>> countries_list = ['Germany', 'Italy', 'Poland', 'France'] >>> len(list(gocept.country.CountrySource(name=countries_list))) 4

python-gocept-0.1-3.lbn25.noarch: gocept python module

python2-tkinter-2.7.17-1.lbn25.x86_64: The Tkinter (Tk interface) program is an graphical user interface for the Python 2 scripting language. You should install the python2tkinter package if you'd like to use a graphical user interface for Python 2 programming.

python2-manuel-1.10.1-1.lbn25.noarch: Manuel lets you mix and match traditional doctests with custom test syntax. Several plug-ins are included that provide new test syntax. You can also create your own plug-ins.

python2-libs-2.7.17-1.lbn25.x86_64: This package contains files used to embed Python 2 into applications.

« Previous 20 items Next 20 items » 1 ... 656 657 658 659 660 661 662 ... 2449


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

Sections

Modified items