-
python-unicodecsv-0.13.0-1.lbn19.noarch
The unicodecsv is a drop-in replacement for Python 2’s csv module which supports unicode strings without a hassle.
More fully
Python 2’s csv module doesn’t easily deal with unicode strings, leading to the dreaded “‘ascii’ codec can’t encode characters in position …” exception.
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 19
-
python-unicodecsv-0.14.1-5.lbn25.py37.noarch
The unicodecsv is a drop-in replacement for Python 2.7's
csv module which supports unicode strings without a hassle.
It is NOT a drop-in replacement for Python 3's csv module,
see https://github.com/jdunck/python-unicodecsv/issues/65
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 25
-
python-unidecode-0.04.1-2.lbn13.noarch
Unidecode
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-unidecode-0.04.19-1.lbn25.py37.noarch
This is a python port of Text::Unidecode Perl module. It provides a function,
'unidecode(...)' that takes Unicode data and tries to represent it in ASCII
characters.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python-unidecode-0.04.19-1.lbn25.py37.noarch
This is a python port of Text::Unidecode Perl module. It provides a function,
'unidecode(...)' that takes Unicode data and tries to represent it in ASCII
characters.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
python-unimr.memcachedlock-0.1rc2_r144828-2.lbn13.noarch
unimr.memcachedlock implements a distributed "soft" locking mechanism using
memcached. It provides factory functions and decorators for a primitive
locking, a reentrant locking and a special locking for zeo-clients.
The native locking methods of python's threading module supports thread safe
locking and therefore, provides only full locking support for single zope
installations. However, zeo-clients have no locking mechanism beetween each
other for concurrent write operations on identical objects (e.g. Catalog) and
are unnecessarily stressed to resolve ConflictErrors on heavy load. The
reason for this problem is the optimistic concurrency control of the ZODB
which primarly prepares the changes of an object (in many cases expensive
calculations) and thereafter checks the validity of the object for the write
process. The higher the number of writes on the same object the higher the
risk that a concurrent zeo-client has already invalidated the object while
another zeo-client has still this object in use. The client with the
invalidated object is constrained to roll back its changes and to recalculate
the changes based on the refreshed object. At worst, this state goes in
circles and results in a ConflictError. The optimistic concurrency control
therefore perfectly fits only concurrent write operations on distinct objects.
Memcache locking overcomes this problem because it extends the regular
concurrency mechanism by a shared locking beetween all involved zeo-clients
by serializing the concurrent write operations before a ConflictError is
provoked. This mechanism is also known as pessimistic concurrency control.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-unimr.memcachedlock-0.1rc2_r144828-2.lbn19.noarch
unimr.memcachedlock implements a distributed "soft" locking mechanism using
memcached. It provides factory functions and decorators for a primitive
locking, a reentrant locking and a special locking for zeo-clients.
The native locking methods of python's threading module supports thread safe
locking and therefore, provides only full locking support for single zope
installations. However, zeo-clients have no locking mechanism beetween each
other for concurrent write operations on identical objects (e.g. Catalog) and
are unnecessarily stressed to resolve ConflictErrors on heavy load. The
reason for this problem is the optimistic concurrency control of the ZODB
which primarly prepares the changes of an object (in many cases expensive
calculations) and thereafter checks the validity of the object for the write
process. The higher the number of writes on the same object the higher the
risk that a concurrent zeo-client has already invalidated the object while
another zeo-client has still this object in use. The client with the
invalidated object is constrained to roll back its changes and to recalculate
the changes based on the refreshed object. At worst, this state goes in
circles and results in a ConflictError. The optimistic concurrency control
therefore perfectly fits only concurrent write operations on distinct objects.
Memcache locking overcomes this problem because it extends the regular
concurrency mechanism by a shared locking beetween all involved zeo-clients
by serializing the concurrent write operations before a ConflictError is
provoked. This mechanism is also known as pessimistic concurrency control.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
python-unittest2-0.5.1-1.fc13.noarch
unittest2 is a backport of the new features added to the unittest
testing framework in Python 2.7. It is tested to run on Python 2.4 -
2.6.
To use unittest2 instead of unittest simply replace ``import unittest``
with ``import unittest2``.
Classes in unittest2 derive from the equivalent classes in unittest,
so it should be possible to use the unittest2 test running infra-
structure without having to switch all your tests to using unittest2
immediately. Similarly
you can use the new assert methods on ``unittest2.TestCase`` with the
standard unittest test running infrastructure. Not all of the new
features in unittest2 will work with the standard unittest test loaders
and runners however.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-unittest2-1.1.0-4.lbn19.noarch
unittest2 is a backport of the new features added to the unittest testing
framework in Python 2.7 and onwards. It is tested to run on Python 2.6, 2.7,
3.2, 3.3, 3.4 and pypy.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
python-unversioned-command-3.10.15-1.lbn36.noarch
This package contains /usr/bin/python - the "python" command that runs Python 3.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
