-
python-m01.grid-0.5.0-2.lbn13.noarch
This package provides a mongodb grid based file implementation for Zope3.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.mongo-0.10.2-1.lbn13.noarch
This package provides a mongodb object mapper framework including zope transaction
support based on some core zope component libraries. This package can get used with
or without zope.persistent and as a full replacement for the ZODB. The package is
not heavy based on zope itself and can get used in any python project which
requires a bridge from mongodb to python object.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.mongofake-1.0.0-1.lbn13.noarch
This package provides a FAKE mongoDB implementation and is quite handy for testing.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.remote-0.5.1-1.lbn13.noarch
This package offers a remote processor. This remote processor is implemented as a simple
object using the mongodb as storage. The processor can execute pre defined jobs in
another thread. It is also possible to run jobs at specific time using the different
scheduler items.
The RemoteProcessor uses two different processor. One processes jobs and the other pickes
items from the scheduler and is adding jobs. This separation is useful if you implement a
distributed concept. This means one or more application can schedule job items based on
the given scheduler items. And another application is processing jobs and doesn't know
about how to scheduling next items.
Since we use this remote scheduler for low CPU intensive jobs, we offer multi processing.
This is done by running more then one worker in the main worker thread. If you use
subprocess for your job processing, you will get a real multiprocessing processor which
isn't limited to the current python process.
You can configure the amount of threads which a job worker can start in the remote
processor. See jobWorkerArguments/maxThreads. By default this number uses the amount of
CPU installed on your machine.
The implementation uses a mongodb as a storage for it's component. This means jobs, job
factories and scheduler items get stored in the mongodb using the ORM concept given from
m01.mongo.
See p01.remote for a ZODB based remote processor implementation but take care the
p01.remote implementation doesn't provide the worker and scheduler processor separation. At
least not yet.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.searcher-0.5.1-1.lbn13.noarch
This package provides a mongodb based search filter implementation for Zope3.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.session-0.5.0-1.lbn13.noarch
This package provides a session implementation based on mongodb for Zope3.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-m01.stub-0.5.7-1.lbn13.noarch
This package provides a mongodb server stub setup for python doctests.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-mailinglogger-3.7.0-2.lbn13.noarch
mailinglogger
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-manuel-1.1.1-2.lbn13.noarch
Manuel lets you build tested documentation.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-markdown-2.0.3-1.fc13.noarch
This is a Python implementation of John Gruber's Markdown. It is
almost completely compliant with the reference implementation, though
there are a few known issues.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
