Saravanan666/pypi-org huggingface dataset:
Package: collective.recaptchawidget
Product information===================This is a simple widget and field for Archetypes that usescollective.recaptcha to show a captcha in any archetypes-based contenttype. Changes to the content type will not be saved if the captcha codeentered by the user is incorrect.To use it, simple define a field in your archetypes schema that lookslike this example::RecaptchaedContentSchema = atapi.Schema((atapi.TextField('Text',storage=atapi.AnnotationStorage(),widget=atapi.TextAreaWidget(label=_(u"Text"),description=_(u"Field description"),),required=True,),CaptchaField('captcha',),))- Code repository: http://svn.plone.org/svn/collective/collective.recaptchawidget- Questions and comments to plone users list.
Package: collective.recipe.ant
ContentsWhat is collective.recipe.ant ?Simple exampleChangelog1.0 (2010-01-05)ContributorsDownloadWhat is collective.recipe.ant ?Collective.recipie.ant executes an ant build. It assumes java, and and ant
is installed on the system.Supported options:antSpecify the location of the ant application. This option is optional.
If not used the application is looked up in the default path.ant-homeIf ant is not located in your defaultPATH-environment variable
you can specify the location here.ant-optionsSpecify the options ant should be called with. You may change the
buildfile with the-buildfileoption for example.classpathGive some extra location for including java libraries.
I.e. junit, …You can debug the ant output by increasing the verbosity of buildout.Simple example>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... """)Ok, let’s run the buildout:>>> print system(buildout)
Installing javaproject.
Build failed
While:
  Installing javaproject.
Error: System error: Buildfile: build.xml does not exist!
<BLANKLINE>
<BLANKLINE>This one failed. We didn’t specify any options. Let’s do that.>>> from os.path import join, dirname
>>> buildfile = join(dirname(__file__), 'testdata', 'echo.xml')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... ant-options =
...     echo
...     -buildfile %s
...
... """ % buildfile)Fetch the output of the ant process, when being extra verbose>>> print system(buildout + ' -v')
Installing ...
<BLANKLINE>
echo:
     [echo] Foo Bar
<BLANKLINE>
BUILD SUCCESSFUL
Total time: 0 seconds
<BLANKLINE>
javaproject: Build successful
<BLANKLINE>Let’s see if the classpath verification works>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... classpath = %s %s
... ant-options =
...     echo
...     -buildfile %s
...
... """ % (join(dirname(__file__), 'testdata'),
...        tmpdir('foo'),
...        buildfile))>>> print system(buildout)
Uninstalling javaproject.
Installing javaproject.
javaproject: Build successful
<BLANKLINE>Now we try to reference a (hopefully) nonexisting directory>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... classpath = %s
... ant-options =
...     echo
...     -buildfile %s
...
... """ % (join(dirname(__file__), '__bogus__dir__'),
...        buildfile))>>> print system(buildout)
Uninstalling javaproject.
Installing javaproject.
While:
  Installing javaproject.
Error: Classpath .../__bogus__dir__ does not exist.
<BLANKLINE>Changelog1.0 (2010-01-05)Initial Release [tom_gross]Removed path checks from __init__() since the required paths may
not be available at that time. [dokai]ContributorsKai Lautaportti (dokai), Author -kai.lautaportti@hexagonit.fiTom Gross -itconsense@gmail.comDownload
Package: collective.recipe.bootstrap
NoteSuperseded byhttps://pypi.python.org/pypi/buildout.bootstrapContentsIntroductionContributorsChanges1.0 (2009-12-19)0.1 (2009-08-07)Code repository:http://svn.plone.org/svn/collective/buildout/collective.recipe.bootstrap/Questions and comments:aclark@aclark.netReport bugs:aclark@aclark.netIntroductionThis recipe satisfies the (perhaps not-so-common) use case of “I want to keep
my buildout bootstrap.py file up to date without having to manually download
it from svn.zope.org.” It also makes it possible to add a bootstrap.py file
to a buildout created viabuildout init. In other words, with this recipe
you can avoid having to do:% svn cat svn://svn.zope.org/repos/main/zc.buildout/trunk/bootstrap/bootstrap.py > bootstrap.pyJust add a newsection, then refer to it in your buildout section’sparts. E.g.:[buildout]
parts =
    ...
    bootstrap

[bootstrap]
recipe = collective.recipe.bootstrapNow whenever you run buildout, this recipe will update your bootstrap.py file.ContributorsAlex Clark, Author [aclark]Changes1.0 (2009-12-19)Clean up docs [aclark]0.1 (2009-08-07)Add initial functionality
[aclark]Created recipe with ZopeSkel
[aclark]
Package: collective.recipe.cmmi
collective.recipe.cmmiExtends zc.recipe.cmmi.Adds`make-options`and`make-binary`.Changelog0.5 - 2013-10-02Allow multiple patch files withpatchesoption.
[fschulze]0.4 - 2013-02-15Fix brown bag release.
[fschulze]0.3 - 2013-02-15Initial release.
[fschulze (Florian Schulze)]
Package: collective.recipe.database_url
collective.recipe.database_urlUsedj-database-urlto parse DATABASE_URL for Buildout environments[buildout]
develop = .
extends =
    https://raw.githubusercontent.com/plock/pins/master/plone-4-3
    https://raw.githubusercontent.com/plock/pins/master/dev
#    https://raw.githubusercontent.com/plock/pins/master/relstorage

# https://raw.githubusercontent.com/plock/pins/master/relstorage
[plone]
eggs +=
    RelStorage
    psycopg2
parts += database_url
rel-storage =
    dbname ${database_url:name}
    host ${database_url:host}
    type ${database_url:engine}
    user ${database_url:user}
    password ${database_url:password}

[database_url]
recipe = collective.recipe.database_urlChangelog0.0.2 (2015-07-04)Update documentation0.0.1 (2015-07-03)Initial release
Package: collective.recipe.distutils
For Python packages which are only installable with distutils, and aren’t
yet available as eggs. This recipe will download a distutils tarball, build it
and place it inside your buildout inside a parts/site-packages directory.It is up to you to inform your Python about this site-packages directory.
You might do this with the zc.recipe.egg recipe:[buildout]
parts =
    mypython

[mypython]
recipe = zc.recipe.egg
eggs = zc.recipe.egg
extra-paths = ${buildout:directory}/parts/site-packages/
interpreter = mypython
scripts = mypythonOptionsurlThe URL of the archives to download and install. The archive specified
will be installed inside a site-packages directory.build_extAdditional build options passed to setup.py.To-DoCurrently only enough work has been done on this recipe to get it to
install mx-base and psycopg2. There is lots of room for improvement …Example UsageA sample buildout.cfg that installs mx-base and psycopg2 inside the
site-packages directory. It also installs PostgreSQL for building
psycopg2, adjusting the build_ext for psycopg2 to point to an existing
PostgreSQL install would remove the need for this:[buildout]
parts =
    egenix-mx-base
    mypython
    postgresql
    psycopg2

[egenix-mx-base]
recipe = collective.recipe.distutils
url = http://downloads.egenix.com/python/egenix-mx-base-3.0.0.zip

[mypython]
recipe = zc.recipe.egg
eggs = zc.recipe.egg
extra-paths = ${buildout:directory}/parts/site-packages/
interpreter = mypython
scripts = mypython

[postgresql]
recipe = zc.recipe.cmmi
url = http://example.com/postgresql-8.1.9.tar.gz

[psycopg2]
recipe = collective.recipe.distutils
url = http://example.com/psycopg2-2.0.6.tar.gz
build_ext =
        --pg-config=${buildout:directory}/parts/postgresql/bin/pg_config
        --rpath=${buildout:directory}/parts/postgresql/lib
Package: collective.recipe.funkload
collective.recipe.funkload is a nice and simple recipe that allows easy running of funkload tests and generation of reports on them,
running ./bin/funkload bench will run all the funkload tests within the buildout and then autogenerate the html reports for them.
Report generation requires gnuplot, currently there is no way to cleanly disable this.  The reports and supporting xml is stored in
the path pointed to by location in your part (defaults to ./var/funkload).  You may also have the reports generated in a different directory
using report_destination.Example usageIn order for this to work its magic you need to set a base URL for the tests
to be run on, your buildout part will look something like this:>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
... index = http://pypi.python.org/simple
... [test1]
... recipe = collective.recipe.funkload
... url = 127.0.0.1:8080
... """)Running that buildout gives us thefunkloadscript:>>> print 'start\n', system(buildout)
start
...
Generated script '/sample-buildout/bin/funkload'.Which passes the host through to the subcommand handler in the recipe:>>> import os
>>> script = os.path.join(sample_buildout,'bin','funkload')
>>> print open(script,'r').read()
#!...url="127.0.0.1:8080"...If you don’t specify a URL buildout will fail:>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
... index = http://pypi.python.org/simple
... [test1]
... recipe = collective.recipe.funkload
... """)>>> print 'start\n', system(buildout)
start
...
KeyError: 'You must specify an address to test'RecordSince version 0.3 you can now use record to create funkload tests even faster:>>> print system('bin/funkload')
Usage:
bench:  Launch a FunkLoad unit test as load test.
record: Launch a TCPWatch proxy and record activities, then output a
        FunkLoad script or generates a FunkLoad unit test if test_name is specified.
report:  Generate a report from the most recent bench result
test:  Launch a FunkLoad unit test.
<BLANKLINE>Change historyHISTORY0.3.1 - 2010-04-19add example usage for PloneFLTestCase
[amleczko]pin collective.funkload to version>0.2
[amleczko]0.3 - 2009-11-23enable test recorder from funkload
[amleczko]update doctests
[amleczko]0.2 - 2009-11-01enable funkload bench to run tests in released eggs [toutpt]0.1 - 2009-08-09Initial releaseAdded funkload script [evilbungle]Added automatic report generation [evilbungle]ContributorsAlan Hoey, [evilbungle]
Tom Lazar, [tomster]
Sasha Vincic, [sashav]
JeanMichel FRANCOIS [toutpt]
Andrew Mleczko, [amleczko]Download
Package: collective.recipe.grp
This is a one line recipe to allow buildout users to refer to${grp:GROUP}to obtain the current user’s UNIX group id.  In other words, the results of:$ id -g -non UNIX systems, for the user executing the buildout. This can be used withgocept.recipe.envto configure ownership of the buildout directory, e.g.:$ chown -R  ${env:USER}:${grp:GROUP} ${buildout:directory}Changelog1.1.0 (2012-04-09)Clean up package
[aclark]1.0 (2011-02-17)Clean up package0.1 (2009-04-03)Added basic functionalityCreated recipe with ZopeSkel
Package: collective.recipe.htpasswd
ContentsIntrodutionExample usageSupported optionsDevelopmentContributorsHistory0.1a3 (2013-03-27)0.1a2 (2013-02-18)0.1a1 (2013-01-30)DownloadIntrodutionThis recipe can be used to generate files for basic authentication of HTTP
users, to restrict the access to HTTP resoruces. The aim is to be fully
compatible with thehtpasswd programthat come with theApache httpd Server, and support all thepassword formatsthat it
supports. This formats, with some minor diffenrences in the case of the plain
method, are alsosupported by the auth_basic moduleof the nginx http server.This recipe support crypt, md5 (APR md5 algorithm), plain and sha1 algorithms
for storage passwords. The crypt algorithm is based on the system’s crypt()
routine, so it inherits its limitations (see:man 5 crypt).Note:The plaintext passowrds are only accepted by the Apache httpd server on
Windows and Netware.Caution:This recipe should not be used to update an existing htpasswd file,
because it overwritte the htpasswd file in every update.Example usageThe simplest way to use this recipe is to add a part inbuildout.cfglike
this:[buildout]parts=htpasswd[htpasswd]recipe=collective.recipe.htpasswdoutput=${buildout:directory}/etc/htpasswdcredentials=nueces:secretnutz:crackmeOne example using thesha1algorithm:[buildout]parts=htpasswd[htpasswd]recipe=collective.recipe.htpasswdoutput=${buildout:directory}/etc/htpasswdalgorithm=sha1credentials=nueces:secretnutz:crackmeFor use themd5algorithm this recipe relies in thepython-aprmd5 package, then to install it you must modify the buildout part
to include the md5extras_requiresetting and install the build depencies
for the python-aprmd5 package. In Debian GNU/Linux the package is thelibaprutil1-dev. It contain the develoment headers of theApache Portable Runtime Utility Library.After that modify the part in thebuildout.cfgit must look like this:[buildout]parts=htpasswd[htpasswd]recipe=collective.recipe.htpasswd [md5]output=${buildout:directory}/etc/htpasswdalgorithm=md5credentials=nueces:secretnutz:crackmeNote:For abug in zc.buildoutif you need to use this recipe with the md5
and the plain or crypt algorithms in two o more parts, you must declare first
the one that use the md5extras_require.Supported optionsoutput: Specify a path to the output file. The path will be created if it does
not exist.credentials: One set per line of credentials formed by username and password
separated by a colon. e.g.<username>:<password>.mode: Specified with octal numbers, as in the chmod program. e.g.640.
If it not set the file are created with the mask mode from the system
enviroment.algorithm: The supported options arecrypt,md5,plainandsha1. Default tocypt.DevelopmentCode repository:http://github.com/collective/collective.recipe.htpasswdReport bugs athttp://github.com/collective/collective.recipe.htpasswd/issuesContributorsJuan A. Diaz (nueces), AuthorHistory0.1a3 (2013-03-27)Added support for the sha1 algorithm.
[Juan A. Diaz (nueces)]0.1a2 (2013-02-18)Added support for the apr md5 algorithm.
[Juan A. Diaz (nueces)]0.1a1 (2013-01-30)Created recipe with ZopeSkelInitial alpha release.
[Juan A. Diaz (nueces)]Download
Package: collective.recipe.hudson
OverviewThis recipe has been superseded byjarn.jenkinsmaintained on Github athttps://github.com/Jarn/jarn.jenkins.This is a recipe to set up and configureHudsonin aJettyservlet container.NoteThe recipe is currently not compatible with Python 2.7 due to an
incompatibility in theiw.recipe.templaterecipe used internally.Basic setupA basic buildout configuration using this recipe looks like this:[buildout]

parts =
    jetty-download
    hudson-download
    hudson

[jetty-download]
recipe = gocept.download
url = http://download.eclipse.org/jetty/stable-7/dist/jetty-distribution-7.0.1.v20091125.tar.gz
md5sum = b29813029fbbf94d05e1f28d9592813f
strip-top-level-dir = true

[hudson-download]
recipe = gocept.download
url = http://download.hudson-labs.org/war/1.375/hudson.war
md5sum = c9bd2515f5b01e46eed2f740aef5e145

[hudson]
recipe = collective.recipe.hudson
jetty-location = ${jetty-download:location}
hudson-location = ${hudson-download:location}This will download both Jetty and Hudson and create an executable Jetty
environment inparts/hudson. It will also create a control script inbin/hudson. The name of the script is the name of the section.To test the setup runbin/hudson fgand check the console output. By default
this will run a Jetty server on port 8070. The hudson instance is accessible in
a browser athttp://127.0.0.1:8070/hudson/.Hudson will write all its log files intovar/hudson/log. All its
configuration including jobs and past runs will go intovar/hudson/data.
The directory name invarwill have the name of the recipe section.OptionsThe recipe supports the following options:hostName or IP address of the Jetty server, e.g.some.server.com.
Defaults to127.0.0.1.portServer port. Defaults to8070.java-optsOptional. Parameters to pass to the Java Virtual Machine (JVM) used to
run Jetty. Each option is specified on a separated line.
If you run into memory problems it’s typical to pass:[hudson]
...
java-opts =
  -Xms512M
  -Xmx1024M
...Changelog1.0 - 2011-02-13Superseded by jarn.jenkins.
[hannosch]1.0a3 - 2010-09-10Added note about Python 2.7 incompatibility. Thanks to Rob Madole for
notifying me.
[hannosch]Updated example to Hudson 1.375.
[hannosch]1.0a2 - 2010-03-04Configure theHUDSON_HOMEenvironment variable inside the jetty.xml
instead of the control script.
[hannosch]Simplify the example buildout a bit.
[hannosch]1.0a1 - 2010-03-04Better update handling.
[hannosch]Don’t configure a ContextDeployer which allows us to skip the contexts
examples cleanup.
[hannosch]Added basic package documentation.
[hannosch]Updated jetty configuration to match new class names caused by the move to
the Eclipse project.
[hannosch]Initial code, largely based on collective.recipe.solrinstance.
[hannosch]
Package: collective.recipe.isapiwsgi
Introduction‘’collective.recipe.isapiwsgi’’ is azc.buildoutrecipe which creates
apaste.deployentry point forisapi-wsgi.It is based on ‘’collective.recipe.modwsgi’’ by Wichert Akkerman.It is very simple to use. This is a minimal ‘’buildout.cfg’’ file
which creates a WSGI script isapi-wsgi can use:[buildout]
parts = isapi-wsgi

[isapi-wsgi]
recipe = collective.recipe.isapiwsgi
eggs = mywsgiapp
config-file = ${buildout:directory}/production.iniThis will create a small python script in parts/isapi-mywsgiapp called
‘’isapiwsgi.py’’ which isapi-wsgi can use. You can also use the optional
‘’extra-paths’’ option to specify extra paths that are added to
the python system path.IIS configuration and installationISAPI-WSGI runs as a DLL inside IIS, which is configured as a wildcard
mapping. The DLL is created from the generated isapiwsgi.py script.To automatically configure IIS, you need to run the script:> cd parts\isapi-wsgi
> python isapiwsgi.py installTo install into a site other than the default, use –server=<name>.If you want this to be run automatically each time buildout is run,
you can give a server name to the recipe:[isapi-wsgi]
recipe = collective.recipe.isapiwsgi
eggs = mywsgiapp
config-file = ${buildout:directory}/production.ini
server = DefaultThe above command will now be run just after the script has been (re-)created.NOTE: If IIS is running whilst you run buildout, you may need to stop the
default application pool so that the DLL file can be re-created.By default, a wildcard mapping is configured at the root of the site
in IIS. If you’d like to configure a virtual directory instead, pass its
name with the ‘’directory’’ option to the recipe:[isapi-wsgi]
recipe = collective.recipe.isapiwsgi
eggs = mywsgiapp
config-file = ${buildout:directory}/production.ini
directory = my-application
server = DefaultLoggingA log file will be written depending on the [loggers] configuration in your
ini file. You may need to ensure that the user which the application pool
in IIS uses has write access to this directory.In addition, you can watch trace messages through the win32traceutil program.
It is installed with the Python Win32 extensions. First, set the ‘’debug’’
option to true:[isapi-wsgi]
recipe = collective.recipe.isapiwsgi
eggs = mywsgiapp
config-file = ${buildout:directory}/production.ini
debug = TrueThen run the trace program:> python -m win32traceutilPackage installationThis recipe does not fully install packages, which means that console scripts
will not be created. If you need console scripts you can add a second
buildout part which useszc.recipe.eggto do a full install.Changelog1.0b1 - 2009-09-18Created new package based on collective.recipe.modwsgi
[optilude]
Package: collective.recipe.jenkinsjob
Introduction============Simple buildout recipe that generated three commands *push a jenkins job*, *pull a jenkins job* and *trigger build on jenkins job*.Recipe enables developer to sync configuration on Jenkins with buildout configuration.Workflow to be used with the recipe:- create and configure a job through the web- run pull jenkins job- later, make more changes the job through the web- run pull jenkins job and use your SCM to diff the config- (optional) push configuration to any other server or use it as restore- (optional) trigger build, because you are too lazy to wait n minutes for cronjobSupported options=================The recipe supports the following options:hostname (required)Hostname of the Jenkins instance.jobname (required)Name of the Jenkins job.jobconfig (default: jenkins_config.xml)Name for XML configuration file for the Jenkins job, relative to buildout directory.username (required)Jenkins usernamepassword (required)Jenkins passwordport (default: 80)Jenkins portExample usage=============We'll start by creating a buildout that uses the recipe::>>> write('buildout.cfg',... """... [buildout]... parts = jenkins-job...... [jenkins-job]... recipe = collective.recipe.jenkinsjob... hostname = %(hostname)s... jobname = %(jobname)s... jobconfig = %(jobconfig)s... username = %(username)s... password = %(password)s... """ % {...     'hostname' : 'jenkins.plone.org',...     'jobname' : 'Plone42',...     'jobconfig': 'plone.xml',...     'username': 'chuck',...     'password': 'norris'})Running the buildout gives us::>>> buildout_output_lower = system(buildout).lower()>>> "installing jenkins-job" in buildout_output_lowerTrue>>> "generated script" in buildout_output_lowerTrue>>> "bin/jenkins-job-push" in buildout_output_lowerTrue>>> "bin/jenkins-job-pull" in buildout_output_lowerTrue>>> "bin/jenkins-job-trigger-build" in buildout_output_lowerTrueDetailed Documentation**********************Contributors************Note:  place names and roles of the people who contribute to this packagein this file, one to a line, like so:- Timo Stollenwerk- Domen KožarChange history**************Changelog=========1.0-alpha1 (2012/02/26)-------------------- forked from collective.recipe.hudsonjob[tisto, iElectric]Download********
Package: collective.recipe.lasso
collective.recipe.lassoThis is a buildout recipe for installinglasso, a C library for single
sign-on, with Python bindings, in a buildout environment.  Lasso supports
SAML 2.0, along with other single sign-on methods.Here is an example of how to use this recipe.  The example includes
recipes for building the libxml2, libxslt, and xmlsec dependencies:[buildout]
parts =
    libxml2
    libxslt
    xmlsec
    lasso

[libxml2]
recipe = zc.recipe.cmmi
url = ftp://xmlsoft.org/XSLT/libxml2-2.7.6.tar.gz
md5sum = 7740a8ec23878a2f50120e1faa2730f2
extra_options = --without-python

[libxslt]
recipe = zc.recipe.cmmi
url = ftp://xmlsoft.org/XSLT/libxslt-1.1.26.tar.gz
md5sum = e61d0364a30146aaa3001296f853b2b9
extra_options = --with-libxml-prefix=${libxml2:location}
                --without-python

[xmlsec]
recipe = zc.recipe.cmmi
url = http://www.aleksey.com/xmlsec/download/xmlsec1-1.2.13.tar.gz
md5sum = f8eb1ac14917f47bc35c265c9d76aaab
# --disable-crypto-dl causes xmlsec to use standard library
# resolution mechanisms rather than its own fragile method.
extra_options = --with-libxml=${libxml2:location}
                --with-libxslt=${libxslt:location}
                --disable-crypto-dl

[lasso]
recipe = collective.recipe.lasso
# see http://labs.libre-entreprise.org/frs/?group_id=31
url = http://labs.libre-entreprise.org/frs/download.php/673/lasso-2.2.1.tar.gz
md5sum = 6548bdb9e334ec075014e68d954948dd
extra_options =
    --with-python=${buildout:executable}
    --with-pkg-config=${libxml2:location}/lib/pkgconfig:${libxslt:location}/lib/pkgconfig:${xmlsec:location}/lib/pkgconfig
    --disable-java
    --disable-php4
    --disable-php5
    --disable-perl
    --disable-gtk-docThis recipe is derived fromzc.recipe.cmmi.  In addition to whatzc.recipe.cmmidoes, this recipe installs the Lasso Python binding
as a fake egg.CHANGES0.1 (2009-10-31)Initial release.