-
collective.z3cform.datagridfield-1.3.3-1.lbn19.noarch
This module provides a z3c.form version of the Products.DataGridField . This product was developed for use with Plone4/5 and Dexterity.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
collective.z3cform.datagridfield-demo-0.5-2.lbn19.noarch
This package provides the demo views for collective.z3cform.datagridfield.
Examples of configurations are in the demo folder. Once you install this package, the
demo views will be visible on your site.
* http://localhost:8080/Plone/@@demo-collective.z3cform.datagrid
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
collective.z3cform.datetimewidget-1.2.9-1.lbn19.noarch
The collective.z3cform.datetimewidget library provides a form framework and widgets. This document ensures that we implement a widget for Date and Datetime field defined in zope.schema. Take a look at the different widget doctest files for more information about the widgets.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
collective.z3cform.mapwidget-2.1-1.lbn19.noarch
Map widget for z3c.form based on collective.geo.mapwidget.
For more information about collective.geo, see the Coactivative home page.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
collective.zamqp-0.14.3-1.lbn19.noarch
collective.zamqp acts as a Zope Server by co-opting Zope's asyncore mainloop (using asyncore-supporting AMQP-library pika), and injecting consumed messages as requests to be handled by ZPublisher (exactly like Zope ClockServer).
Therefore AMQP-messages are handled (by default) in a similar environment to regular HTTP-requests: ZCA-hooks, events and everything else behaving normally.
This package is an almost complete rewrite of affinitic.zamqp, but preserves its ideas on how to setup AMQP-messaging by configuring only producers and consumers.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
collective.zopeedit-1.0.0-2.lbn19.noarch
ZopeEdit : External Editor Client
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
dataflake.cache-1.4-1.lbn19.noarch
This package provides a set of simple cache implementations for use in Python code. Its roots are in the internally-used SimpleCache module from Products.LDAPUserFolder.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
dataflake.ldapconnection-1.5-1.lbn19.noarch
This package provides an abstraction layer on top of python-ldap. It offers a connection object with simplified methods for inserting, modifying, searching and deleting records in the LDAP directory tree. Failover/redundancy can be achieved by supplying connection data for more than one LDAP server.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
dm.profile-1.0-4.lbn19.noarch
"profile.Profile" improvement
I started the implementation of this module in order to improve the profiler's calibration using statistical methods. Unfortunately, variance proved to be far too high and my calibration trials did not converge even for large sample sets. I had to abandon this approach.
The code is still there (in case anyone would like to look what I have tried) but I do not use it.
"pstats.Stats" improvement
Beside the profiler's not so good calibration, I was not satisfied with "pstats" format especially for the caller and callee analysis and with its insistence to write to "stdout".
Therefore, I derived a new class Stats from pstats.Stats and added new methods showStats, showCallers and showCallees which correspond to print_stats, print_callers and print_callees. They write to a file set with setOutputFile (default sys.stdout) and use a different output format. For showCallers and showCallees it is much more readable than the format used by print_callers and print_callees. I am not sure that this is also the case for the format used for showStats versus print_stats.
When you are using "Stats.print_callers" or "Stats.print_callees" and find their output unreadable, then a switch to "dm.profile.Stats" may be profitable for you.
The method showHeader outputs header information (with involved files, top level functions, number of calls and profiled time).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
dm.reuse-1.1-4.lbn19.noarch
Utilities to reuse (slightly modified) oybjects in new contexts.
Currently, there is a single utility: rebindFunction. It allows to reuse the code of a function while changing name, globals, default arguments, properties and/or names used.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
