-
zope-testing-zodb-2.13.30-3.lbn25.noarch
Custom ZODB for Demo(memory) storage
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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``
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-zope.exceptions-4.3-1.lbn25.noarch
zope.exceptions :target:
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-zope.testing-4.7-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python3-numba-0.61.2-1.lbn36.x86_64
Numba is an open source, NumPy-aware optimizing compiler for Python sponsored by Anaconda,
Inc. It uses the LLVM compiler project to generate machine code from Python syntax.
Numba can compile a large subset of numerically-focused Python, including many NumPy
functions. Additionally, Numba has support for automatic parallelization of loops,
generation of GPU-accelerated code, and creation of ufuncs and C callbacks.
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
