Saravanan666/pypi-org huggingface dataset:
Package: collective.recipe.shelloutput
This recipe is for execute shell commands and get the output in another part of
the buildout. The commands are defined in a section called commands, one per
line and the output can be referenced from other parts using the ${…} syntax.>>> write('dummy.py',
... '''
... class Recipe(object):
...
...     def __init__(self, buildout, name, options):
...         self.options = options
...
...     def install(self):
...         if 'output_1' in self.options:
...             print self.options['output_1']
...         if 'output_2' in self.options:
...             print self.options['output_2']
...         return ()
...
...     def update(self):
...         pass
... ''')>>> write('setup.py',
... '''
... from setuptools import setup
...
... setup(name='dummyrecipe',
...       entry_points = {'zc.buildout': ['default = dummy:Recipe']})
... ''')>>> write('buildout.cfg',
... '''
... [buildout]
... develop = .
... parts =
...     shelloutput
...     use-shelloutput
... offline = true
...
... [shelloutput]
... recipe = collective.recipe.shelloutput
... commands =
...     echo_1 = echo 'ECHO'
...     echo_2 = echo 'The shell says: hello.'
...
... [use-shelloutput]
... recipe = dummyrecipe
... output_1 = ${shelloutput:echo_1}
... output_2 = ${shelloutput:echo_2}
... ''')>>> print system(join('bin', 'buildout')),
Develop: '/sample-buildout/.'
Installing shelloutput.
Installing use-shelloutput.
ECHO
The shell says: hello.If we give an empty command we get a hint.>>> write('buildout.cfg',
... '''
... [buildout]
... develop = .
... parts =
...     shelloutput
...     use-shelloutput
... offline = true
...
... [shelloutput]
... recipe = collective.recipe.shelloutput
... commands =
...     empty-cmd =
...
... [use-shelloutput]
... recipe = dummyrecipe
... output_1 = ${shelloutput:empty-cmd}
... ''')>>> print system(join('bin', 'buildout')),
  Develop: '/sample-buildout/.'
  Uninstalling use-shelloutput.
  Uninstalling shelloutput.
  Installing shelloutput.
  Installing use-shelloutput.
  Empty command 'empty-cmd', no output generated.If the execution of a command generates an error, we get the error message.>>> write('buildout.cfg',
... '''
... [buildout]
... develop = .
... parts =
...     shelloutput
...     use-shelloutput
... offline = true
...
... [shelloutput]
... recipe = collective.recipe.shelloutput
... commands =
...     date = date -invalid-option
...
... [use-shelloutput]
... recipe = dummyrecipe
... output_1 = ${shelloutput:date}
... ''')>>> print system(join('bin', 'buildout')),
Develop: '/sample-buildout/.'
Uninstalling use-shelloutput.
Uninstalling shelloutput.
Installing shelloutput.
Installing use-shelloutput.
Error 'date: invalid option ... for command 'date'...Change history0.1 (2010-09-21)Initial release.
[j23d]
Package: collective.recipe.symlink
collective.recipe.symlinkA recipe to enable linking parts of eggs into a fixed directory that can be served via a webserver.UsageExample of the buildout section:[symlink]
recipe=collective.recipe.symlink
egg = foo.bar
destination = ${buildout:directory}/parts/static
links =
  css = foo/bar/static/css
  js = foo/bar/static/jsTODO: TestsChangelog1.0dev (unreleased)Initial release
Package: collective.recipe.vimproject
collective.recipe.vimproject============================:Author:    $Author: seletz $:Date:      $Date: 2008-03-17 16:46:58 +0100 (Mo, 17 Mär 2008) $:Revision:  $Revision: 60824 $Abstract--------This is a recipe to create a VIM project file. This is good for development,and if you use VIM_ with the Project_ plugin.This recipe makes use of the mkvimproject_ egg.code repository: https://svn.plone.org/svn/collective/buildout/collective.recipe.vimproject/trunkUsage-----Just add a buildout section like this::[buildout]parts=vpj[vpj]recipe = collective.recipe.vimprojectpatterns=.py .zcml .pt .cfg .xml .txt .rstcreate_tagfile=yesin_vim_additional=set hlsearchtags=/opt/inquant/buildout/eggs/tags.. _VIM: http://vim.org.. _Project: http://www.vim.org/scripts/script.php?script_id=69.. _mkvimproject: http://pypi.python.org/pypi/mkvimproject/::vim: set ft=rst tw=75 nocin nosi ai sw=4 ts=4 expandtab:Change history**************2008-03-17  Stefan Eletzhofer <stefan.eletzhofer@inquant.de>* setup.py: fixed namespace declaration, added std long_description.* added test setupDetailed Documentation**********************Supported options=================The recipe supports the following options:All options are **optional**.patternsa list of patterns to be included in the project filecreate_tagfileIf this key exists, the recipe wil also use **ctags** to create a tagfile of the buildout directorytagsThis list will be added to the **in.vim** script to set the tag files.Here you can add special directories (like buildout egg caches)in_vim_additionaladditional statements to add verbatim to the **in.vim** script.Example usage=============We'll start by creating a buildout that uses the recipe::>>> write('buildout.cfg',... """... [buildout]... parts=vpj... eggs=mkvimproject... newest=true...... [vpj]... recipe = collective.recipe.vimproject... patterns=.py .zcml .pt .cfg .xml .txt .rst... create_tagfile=yes... in_vim_additional=...  set hlsearch... tags=/opt/inquant/buildout/eggs/tags... """)Running the buildout gives us::>>> print system(buildout)Upgraded:...Installing test1.Unused options for test1: 'option2' 'option1'.Contributors************Stefan EletzhoferDownload********
Package: collective.recipe.z2testrunner
OverviewA zc.buildout recipe for generating test runners that run under a Zope 2
environment and is “Products”-aware.Optionscollective.recipe.z2testrunner has the following options:zope2partname of the script in bin directory to run zope (e. g. zopectl)defaultslist of default options to call zopectl test withenvironmentname of a section which defines variables to be set in environmentmoduleslist of modules to test (arguments for parameter -m)packageslist of packages to test (arguments for parameter -s)extra-pathslist of paths (arguments for parameter –path)exit-with-statusboolean whether to set parameter –exit-with-status or not (default: false)Change History0.3.1Made the exit-with-status option work by actually exiting with the
status code from the test runner [jvloothuis]0.3Added parameters defaults and environmentBugfix: now also works with version specifier added after recipe
name in buildoutAdded documentation in README.txt
[icemac]0.2Add extra-paths and exit-with-status option
[jfroche]0.1Initial implementation.
[rockyburt]
Package: collective.recipe.zcml
collective.recipe.zcmlzc.buildout recipe to create zcml slugs. Useful
for example in a repoze based buildout.Change history0.1 (2008-07-04)Created recipe with ZopeSkel [Stefan Eletzhofer].Detailed DocumentationSupported optionsThe recipe supports the following options:zcmlA list of zcml entires.format:zcml := package ":" filename
package := dottedname | dottedname "-" ( "configure" | "meta" | "overrides" )zope2-locationThe location of the zope 2 installation.The guts of creating ZCML slugs was ripped fromplone.recipe.zope2install.Example usageWe’ll start by creating a buildout that uses the recipe:>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
...
... [test1]
... recipe = collective.recipe.zcml
... zope2-location=${buildout:directory}/zope
... zcml =
...     my.package
...     somefile:my.otherpackage
...     my.thirdpackage-meta
... """)Running the buildout gives us:>>> print 'start', system(buildout) # doctest:+ELLIPSIS
start Installing test1.
While:
  Installing test1.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
<BLANKLINE>
OSError:
[Errno 2] No such file or directory: '/sample-buildout/zope/etc/package-includes'
<BLANKLINE>We need to have a valid zope installation. Let’s fake one:>>> mkdir("zope")
>>> mkdir("zope", "etc")
>>> print 'start', system(buildout) # doctest:+ELLIPSIS
start Installing test1.We now have a package include directory:>>> ls("zope", "etc")
d  package-includesIt does contain ZCML slugs:>>> ls("zope", "etc", "package-includes")
-  001-my.package-configure.zcml
-  002-somefile-configure.zcml
-  003-my.thirdpackage-meta.zcmlThese  files contain the usual stuff:>>> cat("zope", "etc", "package-includes", "001-my.package-configure.zcml")
<include package="my.package" file="configure.zcml" />
>>> cat("zope", "etc", "package-includes", "002-somefile-configure.zcml")
<include package="somefile" file="my.otherpackage" />
>>> cat("zope", "etc", "package-includes", "003-my.thirdpackage-meta.zcml")
<include package="my.thirdpackage" file="meta.zcml" />That’s all.ContributorsStefan Eletzhofer, AuthorDownload
Package: collective.recipe.zmysqlda
collective.recipe.zmysqlda is simple recipe used for installing ZMySQLDA from
the source tarball.
ZMySQLDA 2.0.8 tarball has internal structure lib/python/Products/ZMySQLDA/….
and if you need it in your instance, you must extract it manually.
This buildout recipe solves this problem.Example:[zmysqlda]
recipe = collective.recipe.zmysqlda
target = ${buildout:directory}/productstargetis optional. Defaults to${buildout:directory}/productsPlease note, you need MySQL-python egg in your buildout.cfg or
mysql-python package installed in your python instance.2.0.9Fixed buildout[‘download-directory’]2.0.8Initial release
Package: collective.recipe.zope2wsgi
ContentsDetailed DocumentationWSGI InstanceUsing ZEOContributorsChange historyDownloadDetailed DocumentationThis recipe use plone.recipe.zope2instance and plone.recipe.zope2zeoserver to
generate config files and instances for Zope2 instances / zeo server using
repoze.zope2This mean that you intances are wsgi applications served by PasteDeploy.WSGI InstanceRecipe options are the same thanplone.recipe.zope2instance.The default logging config is override to log toSTDERRinstead of standard
log files.  You can change this by settingevent-log-customandaccess-log-customoptions.We’ll start by creating a buildout that uses the recipe:>>> write('buildout.cfg',
... """
... [buildout]
... parts = instance
... extends =
...     http://dist.plone.org/release/3.3/versions.cfg
...     http://download.zope.org/zope3.4/3.4.0/versions.cfg
... find-links =
...     http://dist.repoze.org/zope2/2.10/
... versions = versions
...
... [instance]
... recipe = collective.recipe.zope2wsgi
... user = admin:admin
... """)Running the buildout gives us:>>> print 'start', system(buildout)
start Installing instance.
Generated config file '/sample-buildout/instance.ini'
Generated script '/sample-buildout/bin/instance'.
Generated script '/sample-buildout/bin/instance.wsgi'.Then you just need to run:$ bin/instance serveThis will launch the application with Paste with the generatedinstance.inifile.You can also use mod_wsgi with theinstance.wsgiscript (this is not tested
but should work).Using ZEORecipe options are the same thanplone.recipe.zope2zeoserver.We’ll start by creating a buildout that uses the recipe:>>> write('buildout.cfg',
... """
... [buildout]
... parts = zeo instance
... extends =
...     http://dist.plone.org/release/3.3/versions.cfg
...     http://download.zope.org/zope3.4/3.4.0/versions.cfg
... find-links =
...     http://dist.repoze.org/zope2/2.10/
... versions = versions
...
... [zeo]
... recipe = collective.recipe.zope2wsgi:zeo
...
... [instance]
... recipe = collective.recipe.zope2wsgi
... user = admin:admin
... zeo-client = on
... """)Running the buildout gives us:>>> print 'start', system(buildout)
start ...
Installing zeo.
Created directory /sample-buildout/parts/zeo
...
Generated script '/sample-buildout/bin/zeo'.
Generated script '/sample-buildout/bin/zeopack'.
Installing instance.
Generated script '/sample-buildout/bin/instance'.
Generated script '/sample-buildout/bin/instance.wsgi'.Then you just need to run:$ bin/zeo start
$ bin/instance serve --daemonContributorsGael Pasgrimaud <gael@gawel.org>Alter WayChange history0.1 (2009-09-04)Initial release
[gawel]Download
Package: collective.redirect301
collective.redirect301Thanks toplone.app.redirectorPlone saves all URL changes that happen in the content and redirects the user to the proper content url.It also allows the content-editor to create custom URLs for the content.When doing so Plone uses aHTTP 302status code to redirect the user to the new URL.Sometimes you want those redirects to return aHTTP 301status code, signaling that the redirect isPermanent.There was a philosophical discussion when the status code was decided and the decission was to return aTemporaryredirect.This addon product, when enabled, changes that behavior and allows returning aPermanentredirect in such cases.InstallationInstall collective.redirect301 by adding it to your buildout:[buildout]

...

eggs =
    collective.redirect301and then runningbin/buildoutFinally you need to go to the Plone Addons Controlpanel and install the product there.AuthorsLur Ibargutxi <libargutxi@codesyntax.com>ContributeIssue Tracker:https://github.com/collective/collective.redirect301/issuesSource Code:https://github.com/collective/collective.redirect301SupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsLur Ibargutxi,libargutxi@codesyntax.comChangelog1.0 (2023-07-19)Initial release.
[libargutxi]
Package: collective.redirectacquired
collective.redirectacquiredThis Plone addon aims to solve the very common issue of having a lot of different URLs that publish the same content item via acquisition.It supports Plone 6. See 1.x branch for Plone 4 support.Zope implicit acquisition leads to many use case where URLs that are valid for the publisher are produced but are not the URLs meant by the users of the system.This addon modifies the publication process to ensure that instead of allowing traversal from a content item to another content item
via  acquisition, we redirect to the URL of the traversed content item.In the previous paragraph, an item is considered a content item if and only if it providesProducts.CMFCore.IContentish.This should avoid false positive redirects for URL path item that are acquired but are actually parts of the software rather than content items.If you need to enable publication of content items via acquisition, mark them withcollective.redirectacquired.interfaces.IPublishableThroughAcquisition.Changelog2.0a1 (2024-02-08)Plone 6 support (Plone 4 support dropped)
[gotcha]NotFound when acquiring site only raised when redirect is activated in zope.conf
[gotcha]1.0a12 (2018-03-20)less noisy logging
[gotcha]NotFound when acquiring a site
[gotcha]1.0a11 (2018-03-12)Be defensive against circular redirects caused by broken Link objects or broken plone.folders
[gotcha]1.0a10 (2018-02-26)Get rid of code made useless by refactoring.
More tests
[gotcha]1.0a9 (2018-02-20)Refactor for more complex acquisitionhttps://github.com/collective/collective.redirectacquired/issues/3[gotcha]Do not break redirectorhttps://github.com/collective/collective.redirectacquired/issues/2[gotcha]Do not allow to cache permanent redirectionhttps://github.com/collective/collective.redirectacquired/issues/1[gotcha]1.0a8 (2018-01-25)Redirect permanently (301)
[gotcha]1.0a7 (2018-01-24)Take care of QUERY_STRING.
[gotcha]Do not redirect if REQUEST_METHOD is not GET.
[gotcha]1.0a6 (2018-01-24)Fix and test when logging only.
[gotcha]1.0a5 (2018-01-24)Fix rushed code.
[gotcha]1.0a4 (2018-01-24)Logging is back.
[gotcha]1.0a3 (2018-01-24)More tests and refactoring
[gotcha]1.0a2 (2018-01-22)More tests
[gotcha]Much simpler implementation
[gotcha]1.0a1 (2018-01-17)Remove useless inclusion of CMFPlone in configure.zcml
[gotcha]1.0a0 (2018-01-17)Initial release
[gotcha]
Package: collective.redirector
collective.redirector is used to redirect links on Plone websites to a specific
page on the same domain or another domain. This packages can redirect both
internal and external links on the Plone websites.
#### Note: collective.redirector is a contenttype (RedirectPage).FeaturesCreate a custom redirect/confirmation page.Allow redirection for external links on any page.Allow redirection for internal links on any page.ExamplesThis add-on can be seen in action at the following sites:
- adding a confirmation page for form submission.
- adding a confirmation page for external links on your plone site, which will allow users to choose if they want to leave your site or not.
- force the user to see a notification or warning page for any links or pages on your site before visiting it.InstallationInstall collective.redirector by adding it to your buildout:[buildout]

...

eggs =
    collective.redirectorand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.redirector/issuesSource Code:https://github.com/collective/collective.redirectorDocumentation:https://github.com/b4oshany/collective.redirector/wikiSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsOshane Bailey,b4.oshany@gmail.com1.1.0Allow redirect to for all external links on any page.Add RegEx url match for links on any site to be redirected.1.0.0Create a custom redirect/confirmation page.Allow redirection for external links on any page.Allow redirection for internal links on any page.
Package: collective.referencedatagridfield
Introductioncollective.referencedatagridfield is a mix of Reference and DataGrid fields for
Plone.  This is a sophisticated reference field with its own widget for adding
and deleting references for both internal and external resources. Having
complete support for Archetype’s Reference field functionality, it also allows
external links management.This package functionality is based on DataGridField, DataGridWidget and
Archetype’s Reference field with ATReferenceBrowserWidget. It allows Plone
developers to extend default Plone Reference field functionality or override
existing Reference field functionality with a custom one.Required Products.DataGridField package is automatically installed during
installation procedure.UsageThis package can be used for extending Plone default Related content
functionality. Apart from possibility to add related items from the current
website, collective.referencedatagridfield allows to:add custom title to the related item instead of its real title add externalsources as related itemsDevelopmentThis product was developed by Quintagroup for Plone collective, sponsored by
Headnet companyhttp://headnet.dk/.Supported Plone VersionPlone 4.0 - 4.2Use CaseThere is an example of simple content type creation with a mix of Reference and
DataGrid fields as related items included into the package:http://svn.plone.org/svn/collective/collective.referencedatagridfield/trunk/collective/referencedatagridfield/examples/ReferenceDataGridDemoType.pyWith this package your content types might get sophisiticated related items
field: include related items from the current site and external ones.1.Internal Links- to insert internal link use ‘Add…’ button and browse
your site for the necessary object you want to add.  Type in desirable title
into the Title field. If you leave it empty - it will automatically be filled
with the inserted object title.2.External Links- to insert external links type in external URL into the
Links field. Type in full address withhttp://protocol.  In case your URL is
not correct it will not be saved. Type in desirable title into the Title field.
If you leave it empty - it will get title the same as URL.AuthorAndriy MylenkyyRoman KozlovskyiVolodymyr CherepanyakThanksgauthier_bastienemaskerLinksSVN Repository -http://svn.plone.org/svn/collective/collective.referencedatagridfieldDocumentation -http://projects.quintagroup.com/products/wiki/collective.referencedatagridfieldChangelog0.5.3 (January, 11 2013)fixed getting field attributes [kroman0]0.5.2 (April, 20 2012)documentation update0.5.1 (April, 20 2012)minor i18n improvements0.5 (September, 12 2011)fixed compatibility issues with Plone 4.10.4 (July 19, 2011)Merged the more-columns branch [chervol]The default title for manual links is the the link [chervol]0.3 (April 4, 2011)Clashing of JS with default referencebrowserwidget fixedMinor fixes in templates and in javascripts0.2 (April 1, 2011)JS fixed for compatibility with archetypes.referencebrowserwidget >= 2.0rc20.1 (May 21, 2010)Initial release
Package: collective.reflex
Tell me what your product doesFeaturesCan be bullet pointsExamplesThis add-on can be seen in action at the following sites:
- Is there a page on the internet where everybody can see the features?DocumentationFull documentation for end users can be found in the “docs” folder, and is also available online athttp://docs.plone.org/foo/barTranslationsThis product has been translated intoKlingon (thanks, K’Plai)InstallationInstall collective.reflex by adding it to your buildout:[buildout]

...

eggs =
    collective.reflexand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.reflex/issuesSource Code:https://github.com/collective/collective.reflexDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsChangelog1.0a1 (unreleased)Initial release.
[]
Package: collective.regenv
collective.regenvThis product allows to override the values stored in the portal registry
and property manager object (i.e. a PAS plugin) with values defined on a local file
defined in an environment variable calledPLONE_REGISTRY_YAML.When it comes to PropertyManager, this product actually only works if you use the accessorgetPropertyto read properties.FeaturesUsing this product you can:have different values for development and production environments
(think about theMailHostsettings,
connection parameters to external services,
etc.)have different values for different instances in the same buildout,
allowing for example to toggle features on and off for A/B testing.DocumentationRegistry overrides should be in a YAML file:% cat sample.yaml

defaults: &defaults
    plone.cachepurging.interfaces.ICachePurgingSettings.cachingProxies:
        - http://localhost:8000
        - http://localhost:8001
    plone.app.theming.interfaces.IThemeSettings.hostnameBlacklist:
        - 127.0.0.1
        - localhost

/Plone/portal_registry:
    <<: *defaults

/Plone2/portal_registry:
    <<: *defaults
    plone.cachepurging.interfaces.ICachePurgingSettings.cachingProxies:
        - http://localhost:9000

/Plone/acl_users/oidc:
    issuer:
        http://localhost:1234/realms/plone/
    client_id:
        ploneRun zope instance with environment pointing to the YAML file, for example:PLONE_REGISTRY_YAML=$(pwd)/sample.yaml bin/instance fgOr using the docker image, for example:docker run -p 8080:8080 \
    -e ADDONS=collective.regenv \
    -e PLONE_REGISTRY_YAML=/app/registry.yaml \
    -v$(pwd)/sample.yaml:/app/registry.yaml \
    plone/plone-backend:latestAlternatively you can add the contents of the YAML file in an environment
variable calledPLONE_REGISTRY_YAML_CONTENTand pass the values directly.
This way you do not need to mount a volume with the configuration file.
For example:export PLONE_REGISTRY_YAML_CONTENT=$(cat sample.yaml)
docker run -p 8080:8080 \
    -e ADDONS=collective.regenv \
    -e PLONE_REGISTRY_YAML_CONTENT
    plone/plone-backend:latestInstallationInstall collective.regenv by adding it to your buildout:[buildout]

...

eggs =
    collective.regenvand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.regenv/issuesSource Code:https://github.com/collective/collective.regenvDocumentation:https://pypi.org/project/collective.regenv/LicenseThe project is licensed under the GPLv2.Contributorsmamico,mauro.amico@gmail.comChangelog1.0.0 (2023-11-15)Add another environment variable to get the YAML file content from
[erral]1.0.0rc1 (2023-03-21)Get overridden keys more efficiently.
[maurits]Fixpython_requiresmetadata.
[maurits]1.0.0a2 (2022-12-27)Fix monkeys init
[mamico]1.0.0a1 (2022-12-27)Initial release.
[mamico]