Saravanan666/pypi-org huggingface dataset:
Package: z3c.locales
This package provides the translation for thez3cpackages which are
using the sharedz3cdomain.ContentsContentsUsageChanges0.3.1 (2010-07-31)0.3.0 (2010-07-08)0.2.0 (2009-12-29)0.1.0 (2009-12-24)ContentsThis package provides translations for:z3c.authviewletz3c.contentsz3c.layer.pageletz3c.tablez3c.wizardUsageInclude theconfigure.zcmlof this package in your project.Changes0.3.1 (2010-07-31)Updated translations for new message id inz3c.table0.8.1.0.3.0 (2010-07-08)Addedcompileextra which requirespython-gettextto ease on
the fly generation of the .mo files.0.2.0 (2009-12-29)Updated author’s email address and home page address.Added z3c.wizard to list of translated packages. Added German
translations for this package.Removed .mo file from distribution.zope.i18nis able to produce
it on the fly (whenpython-gettextis installed, too).0.1.0 (2009-12-24)Currently contains German translations for:z3c.authviewletz3c.contentsz3c.layer.pageletz3c.tableInitial release.
Package: z3c.noop
z3c.noopz3c.noop provides traverser that simply skips a path element,
so /foo/++noop++qux/bar is equivalent to /foo/bar.This is useful for example to generate varying URLs to work around browser
caches[#test-setup]_.>>> dummy = object()
>>> root['foo'] = dummy
>>> traverse('/foo') == dummy
True
>>> traverse('/++noop++12345/foo') == dummy
True[1]>>> import zope.traversing.api
>>> import zope.publisher.browser>>> root = getRootFolder()
>>> request = zope.publisher.browser.TestRequest()>>> def traverse(path):
...     return zope.traversing.api.traverse(root, path, request=request)CHANGES1.0 (2009-06-15)first released version
Package: z3c.objpath
ObjectPathThis package contains two things:thez3c.objpath.interfaces.IObjectPathinterface.some helper functions to construct (relative) object paths, inz3c.objpath.path.The idea is that a particular application can implement a utility that
fulfills theIObjectPathinterface, so that it is possible to
construct paths to objects in a uniform way. The implementation may be
done withzope.traversing, but in some cases you want
application-specific object paths. In this case, the functions inz3c.objpath.pathmight be useful.We’ll have a simple item:>>> class Item(object):
...   __name__ = None
...   __parent__ = None
...   def __repr__(self):
...     return '<Item %s>' % self.__name__Let’s create a simple container-like object:>>> class Container(Item):
...   def __init__(self):
...     self._d = {}
...   def __setitem__(self, name, obj):
...     self._d[name] = obj
...     obj.__name__ = name
...     obj.__parent__ = self
...   def __getitem__(self, name):
...     return self._d[name]
...   def __repr__(self):
...     return '<Container %s>' % self.__name__Now let’s create a structure:>>> root = Container()
>>> root.__name__ = 'root'
>>> data = root['data'] = Container()
>>> a = data['a'] = Container()
>>> b = data['b'] = Container()
>>> c = data['c'] = Item()
>>> d = a['d'] = Item()
>>> e = a['e'] = Container()
>>> f = e['f'] = Item()
>>> g = b['g'] = Item()We will now exercise two functions,pathandresolve, which
are inverses of each other:>>> from z3c.objpath import path, resolveWe can create a path toafromroot:>>> path(root, a)
'/root/data/a'We can also resolve it again:>>> resolve(root, '/root/data/a')
<Container a>We can also create a path toafromdata:>>> path(data, a)
'/data/a'And resolve it again:>>> resolve(data, '/data/a')
<Container a>We can make a deeper path:>>> path(root, f)
'/root/data/a/e/f'And resolve it:>>> resolve(root, '/root/data/a/e/f')
<Item f>The path‘/’leads to the root object:>>> resolve(root, '/')
<Container root>We get an error if we cannot construct a path:>>> path(e, a)
Traceback (most recent call last):
 ...
ValueError: Cannot create path for <Container a>We also get an error if we cannot resolve a path:>>> resolve(root, '/root/data/a/f/e')
Traceback (most recent call last):
 ...
ValueError: Cannot resolve path /root/data/a/f/ez3c.objpath changes2.0 (2023-08-21)Drop support for Python 2.7, 3.5, 3.6.1.3 (2022-12-02)Add support for Python 3.7, 3.8, 3.9, 3.10, 3.11.1.2 (2018-06-14)Add support for Python 3.5, 3.6, PyPy and PyPy3.1.1 (2012-10-13)Add name space declaration forz3c.Added atestextra, as test requirezope.testing.1.0 (2008-04-15)Initial public release.
Package: z3c.offlinepack
Pack ZODBs OfflinePack a ZODB storage without running any part of the Zope application
server.  Only an appropriate version of ZODB3 for the ZODB storage is
required.  Apply only to copies of ZODB storages, not ZODB storages
currently in use.Install the distribution:$ python setup.py installThen use the offlinepack script to pack a copy of your ZODB:$ offlinepack /path/to/Data-copy.fsUse the –help option for more details:$ offlinepack --help
usage: offlinepack [options] PATH...

Pack ZODB storages without running Zope or ZEO

options:
  -h, --help            show this help message and exit
  -d DAYS, --days=DAYS  remove revisions more than DAYS old [default: 0]
  -s DOTTED, --storage=DOTTED
                        use the storage constructor at DOTTED [default:
                        ZODB.FileStorage.FileStorage]zc.buildoutA buildout.cfg is included that will install the offlinepack script
to the buildout.  The buildout makes it possible to quickly use the
offlinepack script without modifying the system python installation:$ git clone https://github.com/rpatterson/z3c.offlinepack.git
$ cd z3c.offlinepack
$ python bootstrap.py -v
$ bin/buildout -v
$ bin/offlinepack /path/to/Data-copy.fsThe buildout.cfg file can also be modified to use a specific version
of ZODB3.  This is uesful if you need to use offlinepack without
migrating the ZODB to a newer version of ZODB3.  Add the version
specifier to the offlinepack section of buildout.cfg.  For example, to
use offlinepack with Zope 2.9, use the following offlinepack section:[offlinepack]
recipe = zc.recipe.egg:scripts
eggs = z3c.offlinepack
    ZODB3<3.7-devChange log0.3 (2014-02-07)Move to GitHub.Added missingzope.testingtest depenency declaration.Added this change log.0.2 (2008-01-26)Initial release.
Package: z3c.optionstorage
Option Storages are vocabularies that store their values in the ZODB and can
be managed during application runtime.CHANGES1.0.7 (2010-02-21)Remove dependency on zope.app.publisher by using a newer zope.browserpage1.0.6 (2010-02-20)Remove dependency on zope.app.zapi and zope.deprecationReplace the use of zope.app.publisher with zope.browserpage1.0.5 (2010-01-04)Remove dependency on zope.app.schema.1.0.4 (2007-11-03)Fix up package meta data.0.1.3 (2007-07-04)Ensure that all package files are included in the egg.0.1.2 (2007-07-04)Bug fix.0.1.1 (2007-07-04)Fix packaging data.0.1.0 (2007-06-22)Initial release.
Package: z3c.profiler
This package provides a profiler skin which allows you to profile pages.Detailed DocumentationWeb-based ProfilerThis package offers a profiler including a skin. This profiler allows
you to profile views on a existing Zope3 application.Let’s access the profiler start page:>>> from z3c.etestbrowser.testing import ExtendedTestBrowser
>>> user = ExtendedTestBrowser()
>>> user.addHeader('Accept-Language', 'en')
>>> user.open('http://localhost/++skin++Profiler')If you access the profiler, you can push the start button:>>> user.getControl('Start').click()
>>> 'Show Profile' in user.contents
TrueNow we can go to thehelp.htmlpage which gets profiled. Let’s use
another browser for this.>>> newBrowser = ExtendedTestBrowser()
>>> newBrowser.open('http://localhost/++skin++Profiler/help.html')
>>> newBrowser.url
'http://localhost/++skin++Profiler/help.html'After calling thehelp.htmlpage, we can go to thedoProfilepage and show the profile by clicking on theShow Profilebutton:>>> user.getControl('Show Profile').click()If we whould not call this form within this test, we whould see the
profile data table. But we do not see the profile data table. Probably
the testrunner conflicts with the monkey call.>>> print user.contents
<!DOCTYPE ...
    <div>
      No data available.
    </div>
...Changes0.10.0 (2010-08-19)Using python’sdoctestmodule instead of deprecatedzope.testing.doctest.Fixedbin/appby requiringzope.login.Removed some not needed dependecies:zope.app.generations,zope.app.pagetemplate,z3c.coverage.Moved dependency onzope.app.serverto anappextra insetup.pyas the tests do not need it and the profiler may be used in a WSGI
application then it is not needed, too.Declaredzope.dublincoreinappextra, too, as it is not needed by
the tests butbin/apprequires now version 3.7 to run.0.9.0 (2009-12-26)Usezope.browserpageandzope.browserresourceinstead ofzope.app.publisher.0.8.1 (2009-12-26)Fixed processing profile data for display in web UI, so the data is
now displayed on the web page. Kept the previous behavior to print
unprocessed profile data onstdout.Removed unused dependency onz3c.i18n.Removed not necessary and undeclared test depenency onzope.app.authentication.Removed zpkg and ZCML install slugs.0.8.0 (2009-06-19)Removed no longer necessary dependencies onzope.app.zapi,zope.app.container,zope.app.component,zope.app.security.Removed dependency onz3c.layer.minimal, as it is not used.Removed no longer necessary test dependencies onzope.app.folder,zope.app.session,zope.app.schema.0.7.1 (2009-04-05)Removed unnecessary dependencies onzope.app.twistedandzope.app.zopeappgenerations.0.7.0 (2009-03-14)Use currentzope.configurationinstead of deprecatedzc.configurationto getexcludedirective.0.6.0 (2009-02-19)No longer uses deprecatedz3c.layer.Fixed dependencies and tests.0.5.1 (2008-01-24)Bug: Fixed meta-data.Bug: Fixed deprecation warning about the Zope Security Policy.0.5.0 (2008-01-21)Initial Release
Package: z3c.pt.compat
This package implements a compatibility-layer between the following
Zope Page Template engines:z3c.ptzope.pagetemplateUsageUse the following import-clause:>>> from z3c.pt.compat import ViewPageTemplateFileIf the environment-variablePREFER_Z3C_PTis set to a true value,
thez3c.ptengine will be used instead ofzope.pagetemplate.Binding methodsTwo methods are available to bind templates and template macros to a
view:>>> from z3c.pt.compat import bind_template
>>> from z3c.pt.compat import bind_macroBoth function return render-methods that accept keyword arguments
which will be passed to the template.>>> render = bind_template(template, view)
>>> render = bind_macro(template, view, request, macro)
Package: z3c.recipe.depgraph
z3c.recipe.depgraphThis buildout recipe generates dependency graphs for packages.OptionseggsThe eggs for which graphs are generated. All dependencies of the eggs are
automatically included.excludeA list of eggs which should be excluded from the graph processing.re-excludeA list of eggs’ regular expressions which should be excluded.dead-endsA list of eggs which dependencies should be excluded.re-dead-endsA list of eggs’ regular expressions which dependencies should be excluded.extrasA boolean determining if extra requirements should be included. Defaults
to False.package-mapAn buildout section containing a mapping of distribution names to package
names.variantsA whitespace separated list of variants of graphs to create. The available
options are:base - The basic full graphs.
tred - The transitive reduction of the graphs.
scc - Extracts graphs of strongly connected components.formatsA whitespace separated list of output-formats to create. Defaults to svg.
Please consult the manpages for the dot-command or visit the graphviz-website
for a fulllist. Most commonly used options are:svg - Scalable Vector Graphics
png - Portable Network Graphics
gif - Graphics Interchange FormatChangelog0.5 (2009-12-21)Do not break if theeggsoption in the buildout file contains extras.0.4 (2009-10-04)Added additionalformatsoption, to control in which file formats the
output is generated.Added additionalre-exclude,dead-endsandre-dead-endsoptions,
to control used eggs more precisely.Added additionalstrictoption, if you want graphs only for eggs in eggs
option.0.3 (2009-07-23)Allow to pass in apackage-mapmanually, mapping distribution names
to different package names.Added additionalextrasoption, to control wether or not extra
dependencies (like test requirements) should be included.Corrected distribution name discovery to preserve case.0.2 (2009-05-24)Do not use-doption for degenerate nodes for sccmap, as this
creates way too much extra information.0.1 (2009-04-26)Initial implementation.
Package: z3c.recipe.egg
Recipes based on zc.recipe.egg for working with source
distributions.Editable DistributionsThe z3c.recipe.egg:editable recipe uses the easy_install –editable
and –build-directory options to download multiple source
distributions.The source distributions will be placed in the part directory and
managed by the buildout if build-directory is not specified.  If so,
the distributions will be replaced when newer versions are available.
So be sure to set build-directory to a directory not managed by
buildout if you want to maintain changes to the source distributions.The z3c.recipe.egg:editable can be used to assemble a set of
subversion checkouts to work with specifying subversion URLs in
find-links as is supported by easy_install.  See the easy_install
documentation for the syntax for using subversion URLs.  There are a
number of ways in which it is more flexible to control checkouts via
recipes rather than svn:externals.Finally, if the develop option is true then the distributions will be
installed in develop mode.See z3c/recipe/egg/editable.txt for more details.Running Setup ScriptsThe z3c.recipe.egg:setup recipe calls arbitrary setup.py commands on
multiple distributions in a buildout.The z3c.recipe.egg:setup recipe can be used, for example, to automate
releases.  When the source is ready for release, the setup recipe is
configured to run the “register sdist bdist_egg upload” setup
commands.  To ensure release only runs when intended, the setup recipe
can be used in it’s own release.cfg file that extends
the buildout.cfg file.  With this setup, releases for multiple
projects can be made with “bin/buildout -c release.cfg”.The z3c.recipe.egg:setup recipe also supports the develop option as
with z3c.recipe.egg:editable.See z3c/recipe/egg/setup.txt for more details.
Package: z3c.recipe.epydoc
IntroductionThis buildout recipe generates epydoc documentation for you projectUsage InstructionsLet’s say you have a package called ezineserver. In the buildout.cfg file of
your package, add adocssection
that looks like this:[docs]
recipe = z3c.recipe.epydoc
eggs =
z3c.recipe.epydoc
ezineserver
doc = ezineserverBe sure to include it in the parts, as in:[buildout]
develop = .
parts = docsNow you can rerun buildout.  The recipe will have created an
executable script in the bin directory calleddocs.This script will run the epydoc documentation generation tool on your
source code.To generate documentation simply rundocsscript:$ ./bin/docsThis generates all the documentation for you and placed it in the
parts directory.  You can then open it up in firefox and take a look:$ firefox parts/docs/index.htmlAnd that’s it!Specify additional optionsIt’s also possible to pass additional epydoc options to thedocsscript (for
a list of all available options, run the script with the--helpoption).You can do this from two different ways:you can pass options directly to the script:$ ./bin/docs --no-frames --include-logor you can use thedefaultsentry to thedocssection:[docs]
recipe = z3c.recipe.epydoc
eggs =
z3c.recipe.epydoc
ezineserver
doc = ezineserver
defaults = ['no-frames', '--include-log']This allows you to create a script with the same options as if you had
specified them on the command line.If not set, thedefaultsentry will default to the value['-v','--debug'].CHANGES0.0.3 (2009-03-10)Add default cli arguments option in buildout.cfg - thanks to Jonathan Ballet0.0.2 (2008-07-09)Pass sys.argv to bin/docs (you can pass additional epydoc options do script)0.0.1 (2008-07-08)Initial release.
Package: z3c.recipe.fakezope2eggs
Zope 2 isn’t eggified yet, Zope 3 does. That can become a problem if you want to
install some egg with depedencies related to Zope 3 eggs (such as zope.interface,
zope.component, …)This buildout recipe will simply add some fake egg link to zope libraries (installed
inside zope/lib/python/zope/…) so that setuptools can see that the dependencies are
already satisfied and it won’t fetch them anymore.Detailed DocumentationHere is the most basic example:>>> write('buildout.cfg',
... """
... [buildout]
... parts =
...     zope2
...     fakezope2eggs
...
... find-links =
...     http://dist.plone.org/
...
... [zope2]
... recipe = plone.recipe.zope2install
... url = http://www.zope.org/Products/Zope/2.9.7/Zope-2.9.7-final.tgz
...
... [fakezope2eggs]
... recipe = z3c.recipe.fakezope2eggs
... """)Now if we run the buildout:>>> print system(buildout)
Installing zope2.
running build_ext
creating zope.proxy
copying zope/proxy/proxy.h -> zope.proxy
building 'AccessControl.cAccessControl' extension
creating build
creating build/temp.linux-i686-2.4
creating build/temp.linux-i686-2.4/AccessControl
...Now if we list all the developped egg we have:>>> ls(sample_buildout, 'develop-eggs')
-  plone.recipe.zope2install.egg-link
-  z3c.recipe.fakezope2eggs.egg-link
-  zope.app.adapter.egg-info
-  zope.app.annotation.egg-info
-  zope.app.apidoc.egg-info
-  zope.app.applicationcontrol.egg-info
-  zope.app.appsetup.egg-info
-  zope.app.authentication.egg-info
-  zope.app.basicskin.egg-info
-  zope.app.broken.egg-info
-  zope.app.cache.egg-info
...Let’s have a look at the content of one of them:>>> cat(sample_buildout, 'develop-eggs', 'zope.app.adapter.egg-info')
Metadata-Version: 1.0
Name: zope.app.adapter
Version: 0.0You might also want to add other fake eggs to your buildout, to do so use the
additional-fake-eggs option, for example:>>> write('buildout.cfg',
... """
... [buildout]
... parts =
...     zope2
...     fakezope2eggs
...
... find-links =
...     http://dist.plone.org/
...
... [zope2]
... recipe = plone.recipe.zope2install
... url = http://www.zope.org/Products/Zope/2.9.7/Zope-2.9.7-final.tgz
...
... [fakezope2eggs]
... recipe = z3c.recipe.fakezope2eggs
... additional-fake-eggs = ZODB3
... """)

>>> print system(buildout)
Uninstalling fakezope2eggs.
Updating zope2.
Installing fakezope2eggs.
<BLANKLINE>Let’s check if the additionnal fake egg exists:>>> cat(sample_buildout, 'develop-eggs', 'ZODB3.egg-info')
Metadata-Version: 1.0
Name: ZODB3
Version: 0.0CHANGESVersion 0.5 (2008-07-21)rename affinitic.recipe.fakezope2eggs to z3c.recipe.fakezope2eggs and
moving it to zope.org reposFeature: Apply patch from Daniel Nouri which add an optional
parameter to skip fake eggs creationVersion 0.4 (2008-03-25)Feature: Apply patch from Bertrand Mathieu which add an optional
parameter to be able to define another zope2 part name (might
not be always “zope2” in every buildout)Version 0.3 (2008-02-19)Feature: Add additional-fake-eggs option which allow you to define
other fake eggs which are not in zope.* or in zope.app.*Version 0.2 (2008-01-28)Bug: Fix zope.app.* bugVersion 0.1 (2007-12-10)Initial Release
Package: z3c.recipe.mkdir
z3c.recipe.mkdirREADMEThis package provides azc.buildoutrecipe used to generate directories
within a buildout.Please seedocs/index.rstfor detailed documentation.Changes1.0 (2023-01-06)Drop support for Python 2.7, 3.4. 3.5, 3.6.Add support for Python 3.8, 3.9, 3.10, 3.11.0.7 (2018-11-16)Add support for Python 3.4, 3.5, 3.6, 3.7, PyPy and PyPy3.Drop support for Python 2.6, 3.2 and 3.3.0.6 (2013-05-21)Dropped support for deprecatedpathoption (usepathsinstead).Added support for Python 3.2 / 3.3.Addedsetup.py docsalias:  runssetup.py developand then installs
documentation dependencies.Addedsetup.py devalias:  runssetup.py developand then installs
testing dependencies.Updated docs and tests.0.5 (2012-06-26)Added support forcreate-intermediateoption (yesby default).Fixed bug: empty directory names were not excluded frompaths.0.4 (2012-06-24)Added support formode,user, andgroupoptions.Fixed (unnoticed?) bug when using the deprecatedpathoption. In
that case the default path (parts/<sectionname>) was created
instead of the given one.Shortened main code.Updated tests to run withzc.buildout1.5, thus requiring at least this
version.Using python’sdoctestmodule instead of depreactedzope.testing.doctest.0.3.1 (2009-08-21)Update optionspathandpathsto be referencable.Outputcreatedmessage only if a directory was really created
but display this message also for intermediate directories.0.3 (2009-08-20)Renamedpathoption topaths(plural). Please do not usepathanymore!Created directories are now displayed during buildout runs.Changed default behaviour: directories created once will not be
removed on updates, except you require that explicitly.Added new optionremove-on-update: if set toyes,trueoronthe set directories will be removed on updates ofbuildoutconfiguration.0.2 (2009-08-19)Make paths absolute and normalize them before creation.Support creation of several paths in a row.Added check whether a file exists as part of path and emit error.0.1 (2009-08-17)Initial release.
Package: z3c.recipe.openoffice
This recipe download openoffice in your buildout, it can also (optional)
create egg with pyuno and change the default python used by openoffice.More info about Python UNO:http://udk.openoffice.org/python/python-bridge.htmlWe are using this to generate OpenOffice documents from zope/pythonBuildout configuration:Add this section to your buildout configuration:[buildout]
parts =
    ... your other parts ...
    openoffice
...

[openoffice]
recipe = z3c.recipe.openofficeThis will just download and install openoffice in your buildoutTo create the pyuno egg add the fallowing config:[openoffice]
recipe = z3c.recipe.openoffice
install-pyuno-egg = yesTo also change openoffice python, add the following config:[openoffice]
recipe = z3c.recipe.openoffice
install-pyuno-egg = yes
hack-openoffice-python = yesBy default it will fetch version OpenOffice 2.3 but you might want to install from another location or another version like this:[openoffice]
recipe = z3c.recipe.openoffice
install-pyuno-egg = yes
hack-openoffice-python = yes
version = 2.3.1
download-url = ftp://ftp.openoffice.skynet.be/pub/ftp.openoffice.org/stable/2.3.1/OOo_2.3.1_LinuxIntel_install_en-US.tar.gzNotes:For this to work an OpenOffice process need to be running in background. As this require a X server and you don’t want to install a real X server in a production environment you might want to use Xvfb. Here are the lines we use to start openoffice:$ cd myBuildout
$ Xvfb :3 -ac -screen sn 800x600x16 &
$ ./parts/openoffice/program/soffice "-accept=socket,host=localhost,port=2002;urp;" -display :3 &
$ ./bin/instance startThis recipe only works with linux at the momentTo test pyuno (requires zopepy in buildout.cfg):$ ./bin/zopepy
>>> import pyunoIf you get the fallowing error:"SystemError: dynamic module not initialized properly"Do:$ ldconfig YOURBUILDOUTFOLDER/parts/openoffice/programIf you still face the same error, you might try:$  export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"YOURBUILDOUTFOLDER/parts/openoffice/program"Be careful that the first time you will run soffice in server mode, openoffice will oblige you to pass throught a wizard run first openoffice on your
normal display or copy an .openoffice2 folder in the home of the user which is running the command.This recipe requires rpm2cpio and cpio to be installed on your system.Authors:Original author: Martijn Faassen -faassen@infrae.comModified by: Jean-Francois Roche -jfroche@affinitic.be
Package: z3c.recipe.perlpackage
Recipe for installing Perl packages via downloadThe perlpackages recipe automates installation of Perl packages.This recipe is similar to zc.recipe.cmmi, but instead of performing
“configure, make, make install” it uses “perl Makefile.PL” for the configure
step.OptionsurlLocation to download the Perl distribution from.extra_optionsAdditional parameters that are passed to Makefile.PL.perlName of the Perl interpreter to use for “perl Makefile.PL”. Defaults
to “perl”.flatinstallprefixSet the installation prefix, and force all library, doc and bin files to
be flattened into three install locations:${flatinstallprefix}/lib/perl5/
${flatinstallprefix}/bin/
${flatinstallprefix}/man/This is suitable for creating a location that you can include in your
PERL5LIB environment variable.Release History0.1 (2008-07-04)Initial release.