Saravanan666/pypi-org huggingface dataset:
Package: plone.recipe.haproxy
ContentsSupported optionsExample usageReporting bugs or asking questionsCode repositoryContributorsReleases2.0.0 (2021-05-07)2.0rc1 (2021-02-25)1.1.2 (2012-01-26)1.1.1 (2010-10-06)1.1 (2010-04-25)1.0 (2010-04-25)1.0b3 (2010-01-20)1.0b2 (2010-01-12)1.0b1 (2008-11-25)Supported optionsAttention: Python3 only version! If you’re using Python2 you have to pin
this package version to <2.0.0.This recipe supports the following options:urlURL pointing to thehaproxycompressed archive. By default it uses:http://www.haproxy.org/download/2.1/src/haproxy-2.1.3.tar.gztargetTarget can be one of the following:
linux22, linux24, linux24e linux24eold, linux26, solaris, freebsd,
openbsd, generic.cpuCPU can be one of the following: i686, i586, ultrasparc, generic.pcreSet to1to enable the use of the PCRE library.Example usageTo use this recipe, just create a part for it and define therecipeparameter:[buildout]
parts =
    ...
    haproxy

[haproxy]
recipe = plone.recipe.haproxyThis will configure the default options forurl,target,pcre, andcpu. If you like or need to you can override these parameters, e.g.:[haproxy]
recipe = plone.recipe.haproxy
url = http://my.dist.server/haproxy-1.x.y.zip
target = linux26
cpu = i686
pcre = 1Reporting bugs or asking questionshttps://github.com/plone/plone.recipe.haproxy/issuesCode repositoryhttps://github.com/plone/plone.recipe.haproxyContributorsHelge Tesdal, Author [tesdal]Alex Clark [aclark]Hanno Schlichting [hannosch]Releases2.0.0 (2021-05-07)Updated setup.py.2.0rc1 (2021-02-25)Set haproxy 2.1 as default version
[erral]Update to support python3 only
[erral, petschki]1.1.2 (2012-01-26)Force the use of gmake on freebsd.
[lregebro]When there the Makefile is in a deeper dir the make with options is never
executed
[kingel]1.1.1 (2010-10-06)Update to haproxy 1.4.8.
[hannosch]Fix bug withinstall_from_cachethat prevents downloading haproxy if it
is not already present in the cache.
[silviot]1.1 (2010-04-25)Default tohttp://dist.plone.org/thirdparty/haproxy-1.4.4.zip. Make sure
your configuration files are compatible with the new release before
upgrading.
[hannosch]1.0 (2010-04-25)PEP8 cleanup, avoid deprecation warning for the sha module under Python 2.6.
[hannosch]Updated tests, removed test extras and dependency on zope.testing.
[hannosch]1.0b3 (2010-01-20)Usehttp://dist.plone.org/thirdparty/haproxy-1.3.22.zipas the default
url. The tarfile module in Python 2.4 cannot open the official releases, so
we provide a zip alternative for it.
[hannosch]Further package metadata cleanup. Moved tests outside of the package
description.
[hannosch]1.0b2 (2010-01-12)Clean up documentation, reorganize package contents.
[aclark]Don’t forcemake-fMakefile.osxon OS X, fixes Snow Leopard compilation.
[aclark]1.0b1 (2008-11-25)First public release.
[tesdal]
Package: plone.recipe.lxml
NotesThis recipe is only tested with Debian, Gentoo and minitage. Thez3c.recipe.staticlxmlrecipe is better maintained.OptionseggThe desired lxml egg version (likelxml==2.2.6).libxslt-urlThe URL to download the libxslt tarballe, the default value is:
‘http://xmlsoft.org/sources/libxslt-1.1.26.tar.gz’libxml2-urlThe URL to download the libxml2 tarball, the default value is:
‘http://xmlsoft.org/sources/libxml2-2.7.7.tar.gz’Example buildout configuration[buildout]
parts = lxml
eggs = lxml == 2.2.6

[lxml]
recipe=plone.recipe.lxml
egg = lxml == 2.2.6
Package: plone.recipe.osxcontroller
This zc.buildout recipe installs an OS X, wxPython-based visual controller for Plone.Typical usage in a Plone buildout:parts=
    ...
    osxcontroller
    ...

[osxcontroller]
recipe = plone.recipe.osxcontrollerCode repository:http://svn.plone.org/svn/collective/buildout/plone.recipe.osxcontrollerQuestions and comments to:setup@lists.plone.orgmailing list.Report bugs athttps://dev.plone.org/plone- component Installer, OS X.Detailed DocumentationExample usageWe’ll start by creating a buildout that uses the recipe:>>> write('buildout.cfg',
... """
... [buildout]
... parts = controller
...
... [controller]
... recipe = plone.recipe.osxcontroller
... """)Running the buildout gives us:>>> print 'start', system(buildout)
start...
Installing controller.
<BLANKLINE>Let’s look for the symlinks to our app:>>> ls(sample_buildout)
-  .installed.cfg
d  PloneController.app
d  bin
-  buildout.cfg
d  develop-eggs
d  eggs
d  partsContributorsSteve McMahon, AuthorChange history0.4 (2010-03-15)Adapt to Plone 4 by removing separate buttons for viewing Plone and Zope.0.3 (2009-09-08)Change wait times to account for odd status replies0.2 (2008-12-16)Change to copy controller app to dest [Steve McMahon].0.1 (2008-11-30)First release [Steve McMahon].
Package: plone.recipe.plone
This recipe allows you to install Plone, based on the packages used for the
Plone installers.Here is an example buildout:[buildout]
parts = plone zope2 instance
eggs =
develop =

[plone]
recipe = plone.recipe.plone

[zope2]
recipe = plone.recipe.zope2install
url = ${plone:zope2-url}

[instance]
recipe = plone.recipe.zope2instance
zope2-location = ${zope2:location}
user = admin:admin
http-port = 8080
debug-mode = on
verbose-security = on
eggs =
    ${buildout:eggs}
    ${plone:eggs}
zcml =

products =
    ${plone:products}
    ${buildout:directory}/productsNotice how the ‘plone’ recipe is able to supply a URL for a “known good”
version of Zope (you can of course choose not to use it).The ‘instance’ recipe is configured with two parameters set by the ‘plone’
recipe:plone:eggs – The various Plone eggsplone:products – A directory containing the Plone Zope 2 productsOther possible options in the ‘plone’ section include:eggs – Override the eggs used by Plone. If you specify an egg here that isalso part of the standard Plone distribution, the specified egg will
override the default. For example, if you want to track svn for a
particular egg, check it out to the src/ directory, add a line to
‘develop’ in buildout (e.g. “develop = src/plone.theme” to track the
plone.theme package) and then add “eggs = plone.theme” to the ‘plone’
section. Alternatively, if you need to upgrade or downgrade a particular
egg, you can do so with a version specification.find-links – Specify one or more find-links for setuptools to downloadeggs from. By default, this includeshttp://dist.plone.organd any
find-links specified in the main [buildout] section.urls – A list of URLs to download packages from, overriding those from theinstaller configuration. You can use the options ‘nested-packages’ and
‘version-suffix-packages’ to give the names of download archives which
contain a parent directory and the actual product in a sub directory,
and products which when extracted have a directory containing the version
number. See plone.recipe.distros for more information.zope2-url – Override the Zope 2 URL from the installer (not that there ismuch point in doing so).
Package: plone.recipe.precompiler
Buildout recipe to precompiles Python and locale files in an egg list.Why precompilation?Python ordinarily compiles .py files into .pyc or .pyo byte code files
on demand. Likewise, applications like Plone often compile .po locale
files into .mo representations when needed.However, if you are running a Python application as a daemon and wish
to prevent write access to code directories, you want to do these
compilations at buildout-time, not run-time. That’s where this recipe
comes in. Passed an egg list, it will pick up all the eggs in the
buildout working set for the list and find and compile .py and .mo
files in place..mo file compilation is optional, and must be turned on.UsagePlease note that usage changed with release 0.5. If you need the old
options, use 0.4Common usage:[buildout]
parts =
    ...
    precompile
eggs = ...


[precompile]
recipe = plone.recipe.precompiler
eggs = ${buildout:eggs}
compile-mo-files = trueThis recipe may return harmless warnings regarding the inability to compile skin
layer scripts, which typically have “return” outside of a function. While these
warnings are harmless, you may suppress them by tuning the skip list.Optionsrecipe = plone.recipe.precompiler

eggs = required: list of eggs

compile-mo-files = true/false; default is false

extra-paths = optional list of additional paths
    that would not be found from eggs
    in multiple
    indented lines

quiet = true/false; if true, common errors are only shown when buildout's
    verbose flag is set.NotesThis recipe was created for use in Plone installers, but is hopefully useful in
many buildout contexts.Change historyChangelog for plone.recipe.precompiler.0.7.2 (2020-06-26)Bug fixes:Small packaging updates.  [gforcada, jensens, maurits]0.7.1 (2018-11-11)Bug fixes:Rerelease to fix Python 3 issue in 0.7
[esteele]0.7 (2018-11-07)Bug fixes:Fix reversion in 0.6, displaying too many .po compile errors.0.6 (2012-12-17)Use python_gettext rather than msgfmt to compile .po files. Removes
dependence on gettext.
(smcmahon)0.5Suck up error messages and filter them to hide .po compile errors
and .py “return outside function” errors when quiet option is true (default).
(smcmahon)Make the extra-paths work with the new working set method for finding eggs.
(smcmahon)Removed BBB code. The new way of finding eggs introduced by chaoflow is much
better than my original.
(smcmahon)removed the functionality to automatically extract products directories from
parts with the zope2instance recipe. This resulted in buildouts that always
installed ALL parts. If you need the products dir, you must declare it explicitly
like so: dirs = ${instance:products}
(do3cc - 2012-07-12)0.4 (2010-08-12)support for walking eggs dependencies, without skip/rx, manually tested.
(chaoflow - 2010-08-12)support for compiling mo files in those egg dirs, manually tested.
(chaoflow - 2010-08-12)kept old syntax and code, just don’t specify eggs (untested)0.3support to recursively compile list of dirs, with subdir blacklist and file
blacklist regex.
(Steve McMahon)ContributorsSteve McMahon <steve@dcn.org>Florian Friesdorf <flo@chaoflow.net>
Package: plone.recipe.runscript
Plone Runscript RecipeAbstractThis is a buildout recipe for zope/plone which runs a script
usingzopectlin a zope instance.Recipe optionsinstance-homeThe INSTANCE_HOME. This can commonly be found in the ${instance:location}
buildout variables.zeo-homeIf you are using a zeo server then you must define this option so zopectl
can connect to your database.  This can commonly be found in the
${zeoserver:location} buildout variable.scriptThe path to the script that will be run. If not specified the script name
is taken form the part name with a.pysuffix added  and assumed to be
location in ${buildout:bin-directory}.argsThe arguments for the script.The script is run using the instance startup script, which is assumed to be
named like the basename part of the instance-home directory.Changes0.3.1 2009-03-08Removed SVN tags – dont need no more SPAM [seletz]0.3 2009-03-08Long overdue release [seletz]added support for zeo by adding a ‘zeo-home’ option which works in the same
manner as the ‘instance-home’ option. the zeo is started and then stopped
once the script has been run. [claytron]Document the .py suffix default [wichert]Allow specifying a custom script as well [wichert]Expand the documentation a little bit [wichert]
Package: plone.recipe.unifiedinstaller
This recipe is used by the Unified Installer Buildout to do finishing work like
writing the adminPassword.txt and ZEO control scripts.Please file bugs tohttps://dev.plone.org/plone/newticketand specify
the component “Installer (Unified)”.Tests for this recipe are in the Unified Installer.Optionsshell-commandFull pathname to a POSIX-compliant shell. Used in ZEO start, stop, etc. scripts.
Default: /bin/shsudo-commandCommand – if needed – to run process as root. Used only in adminPassword.txt.
Default: ‘’zeoserverName of the ZEO server part if any. If missing, the recipe will scan other
buildout parts for one using plone.recipe.zope2zeoserver and use its name.
If a zeoserver is specified or found, ZEO start, stop, etc. scripts will
be written.clientsNames of Zope client parts in the buildout. If missing, the recipe will
scan other buildout parts for one using
plone.recipe.plone.recipe.zope2instance and use their names.primary-portPort of the primary client instance. Used in the adminPassword.txt file.
Default: 8080userUser name and password for the initial Zope administrator. Use
the format “user:password”
Default: None. Must be specified.Change Log4.3.2Fix bug that caused failure in buildout if clients were directly specified.
[smcmahon]4.3.1Fix bug that prevented plonectl from starting in a non-zeo configuration.
[MatthewWilkes]4.3Add new options to handle separate daemon and buildout
users.Check parts list in a way that doesn’t force building of
every part.Remove backward compatability code that created specific
function scripts for start/stop/status.4.0rc1Remove documentation for buildout -n. Add sudo to bin/buildout
for root installs.When stopping a ZEO cluster, stop the server last.4.0b3Add ‘console’ command.Add .html readme.4.0a1Remove automated creation of Plone site.0.9Revert damaged logo.0.8Take buildout:parts-directory into account when writing out
parts/README.txt. Fixes #9242, Thanks, cah190.Callcommand-script.py with the current sys.executable if it
exists, as to run it with pythonw.exe during the Plone Windows
installer’s install.0.7Quote arguments when init’ing plone site in case
module path has space(s).0.6Add “plonectl” general-purpose control script.Add facility to install plone_init_content0.5Check the directory, not the file. The directory may not
exist.0.4Have all the cluster scripts check permissions on var
before proceeding.0.3Split adminPassword.txt and README.txt files. Enhance README.Add bin/restartclients.sh script to restart clients only.0.2Refactored templates and bin scripts into separate files.Restored restartcluster.sh (fixes #7692, thanks Graham Perrin).
Package: plone.schema
Provides additional fields and widgets for z3c.form and optional integration with Plone.Email Field and WidgetJSON Field and WidgetURI Field and WidgetIPath as IChoice derivative (and implementation)integration with plone.supermodel, optional (extra “supermodel”)integration with plone.schemaeditor, optional (extra “schemaeditor”)Source CodeContributors please read the documentProcess for Plone core’s developmentSources are at thePlone code repository hosted at Github.2.0.1 (2023-10-07)Internal:Update configuration files.
[plone devs] (cfffba8c)2.0.0 (2023-04-06)Breaking changes:Drop Python 2 support.
Housecleaning: pyupgrade, isort, black.
Introduce extrasplone.schema[supermodel]andplone.schema[schemaeditor].
The package works in its vanilla installation as an addon for z3c.form, without any other plone dependencies.
[jensens] (#17)Bug fixes:Fix #12: no transitive circular dependency overplone.app.z3c.formanymore.
This removes the registration onIPloneFormLayerand uses the base layer of z3c.formIFormLayer.
[jensens] (#12)Internal:Update configuration files.
[plone devs] (93ecbf56)1.4.0 (2022-04-28)New features:Use indent in json.dumps to make JSON readable in the widget [MrTango] (#16)1.3.0 (2021-03-24)New features:Adjust JSONField to include widget name
[sneridagh] (#10)1.2.1 (2020-04-22)Bug fixes:Minor packaging updates. (#1)Fix JSONField with default values saved tomodel_sourceXML
[avoinea] (#7)Initialize towncrier.
[gforcada] (#2548)1.2.0 (2018-06-24)New features:Improve and complete Plone integration of the JSONField (z3c.form, plone.supermodel, plone.schemaeditor)
[sneridagh]1.1.0 (2018-06-23)New Features:Add new JSONField field and JSONSchema auto validation.
[sneridagh]1.0.0 (2016-02-25)Fixes:Moved translation to plone.app.locales
[staeff]Fixed install_requires to specify correct dependencies.
[gforcada]1.0a1 (2014-04-17)Initial release.
[ianderso,davisagli,frapell]
Package: plonesocial.auth.rpx
plonesocial.auth.rpxplonesocial.auth.rpxis an addon product for Plone which allows users
to authenticate via theJanRain’s RPX service. RPX is
sort of a proxy to let a user authenticate with a lot of identity services such
as OpenID, Twitter, Facebook and many others.Different from the OpenID plugin for Plone the RPX plugin does not just create a virtual user but instead it will map the verfied identifier from RPX (e.g. your OpenID) to an existing or to be created user account. A user is also able to map various identifiers to the same Plone account thus being able to login with his Twitter, Google or Facebook account to the same Plone account.plonesocial.auth.rpxalso allows the user to manage those mappings.DocumentationThe full documentation can be found athttp://comlounge.net/rpx/Please report bug athttp://bitbucket.org/cryu/plonesocial.auth.rpx/issues/CreditsCarsten Rebbien (main programming,cr@comlounge.net)Christian Scholz (concept, bugfixing and documentation,cs@comlounge.net)Source CodeThe source code is available athttp://bitbucket.org/cryu/plonesocial.auth.rpx/LicenseCopyright (c) 2010 COM.lounge GmbHPermission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.Change history0.815 - (2010/03/15)initial releaseDownload
Package: plonesocial.buildout
ContentsIntroductionPlonesocialUsing this buildoutMakefileGithub sourcesIntroductionThis is a developer’s buildout to work on the Plonesocial suite of packages.PlonesocialPlonesocial consists of:plonesocial.microblogStatus updatesplonesocial.activitystreamLists content changes, discussion replies, and status updatesplonesocial.networkFollow/unfollow of usersplonesocial.likeFavoriting of contentplonesocial.suiteAn out-of-the-box social business experience integrating all of the above.
If you’re an end user, this is what you’re looking for.plonesocial.buildoutThis buildout. Not a Python package. Intended for Plonesocial developers only.This is a work in progress and not suitable for general release yet.Using this buildoutYou can ignore the Makefile and just use buildout. You’ll have to bootstrap
it first though. YMMV. See the Makefile for scripts.MakefileThe included Makefile is optimized for use on Ubuntu Lucid:make lucid
makeGithub sourcesBy default, the buildout clones read-only sources of the various plonesocial.* components
into ./src/. To enable push, create a fork on github and then:cd ./src/plonesocial.microblog
git remote set-url --push origin git@github.com:YOUR_GITHUB_ID/plonesocial.microblog.gitYou’ll have to to that for each src package you want to push, and/or for the buildout itself.Please don’t forget to submit pull requests :-)
Package: plonesocial.theme
Introduction============Plone theme based on Twitter Bootstrap 2.0.This theme is intended to be used with the `PloneSocial suite`_... _PloneSocial suite: https://github.com/cosent/plonesocial.suiteCredits-------|Cosent|_Plonesocial.theme is maintained by Cosent_.This package is forked from `diazotheme.bootstrap`_ by Izhar Firdaus... _Cosent: http://cosent.nl.. |Cosent| image:: http://cosent.nl/images/logo-external.png:alt: Cosent.. _diazotheme.bootstrap: https://github.com/kagesenshi/diazotheme.bootstrapInstallation============Install the ``plonesocial.theme`` product using the Add-on Control Panel.This will activate the theme and also setup Plone's default ``public.css``to only included when Diazo is enabled or when you are viewing the ThemingControl Panel. This theme includes its own ``public.css`` which had severalitems from the default ``public.css`` removed.Features=========* Turn your site into a pretty Bootstrap based theme, and also simplifiestemplating of customization addons.* Portlets are converted to ``div`` elements instead of ``dl``, ``dt``, ``dd``* ``presentation_view`` is enhanced with Google's HTML5 slides* Included carousel portlet provides a way to display images using Bootstrap'scarousel* ``eea.facetednavigation`` is also supported, with some enhancements.* The diazo rules rewrite facetednavigation templates to take advantage ofthe responsive design.* If the first widget at the top widget slot is a text search widget, it willappear as a full width widget with a different background.* Installing ``webcouturier.dropdownmenu`` will enhance the top navigation withdropdown menus.Using Bootstrap javascripts===========================This product leaves plone jquery alone not to break existing functionality.But bootstrap requires a newer jQuery version. We include the needed one renaming it to jQuery17.If you need js functionality from bootstrap you have to use jQuery17, for instance$(function() {jQuery17('.tooltipped').tooltip()});to activate the tooltip plugin on elements with the class "tooltipped".Changelog=========0.5.4 (2014-03-11)------------------* bring theme inline with changed plonesocial.activitystream navigation markup [gyst]0.5.3 (2013-07-31)------------------* better profile name [gyst]0.5.2 (2013-07-31)------------------* bump version to resolve tag/setup mismatch [gyst]0.5.0 (2013-07-04)------------------* update docs [gyst]* Remove carousel portlet. This fixes all pep8 violations. [Guido A.J. Stevens]* extract navigation to separate block [Guido A.J. Stevens]* fix breadcrumb spacing [Guido A.J. Stevens]* style footer more elegantly [Guido A.J. Stevens]* provide and fall back to hardcoded footer [Guido A.J. Stevens]* simplify by removing ContentWellPortlets support [Guido A.J. Stevens]* integrate plonesocial subnav [Guido A.J. Stevens]* fork from diazotheme.bootstrap [Guido A.J. Stevens]0.4 and earlier---------------See https://github.com/kagesenshi/diazotheme.bootstrap
Package: plonesocial.twitter.anywhere
Introductionplonesocial.twitter.anywhereintegrates Twitter’s @Anywhere platform into Plone.It allows you to doautomatic linking of @username to their twitter pageautomatic hovercard display on @username which allows the user to automatically follow that user.add portlets with a Follow buttonadd portlets with a tweetboxMore features to come!You can find the complete documentation athttp://comlounge.net/anywhereChangelog0.1 - 2010/05/11Initial releaseDownload
Package: plone.synchronize
IntroductionThis package provides a simple decorator to help synchronize methods across
threads, to avoid problems of concurrent access.It can be used like this:from threading import Lock
from plone.synchronize import synchronized

class StupidStack(object):

    _elements = [] # not thread safe
    _lock = Lock()

    @synchronized(_lock)
    def push(self, item):
        self._elements.append(item)

    @synchronized(_lock)
    def pop(self):
        last = self._elements[-1]
        del self._elements[-1]
        return lastThe decorator takes care of calling lock.acquire() just before the method
is executed, and lock.release() just after. If an exception is raised in the
method, the lock will still be released.Changelog1.0.4 (2020-04-22)New features:Drop Python 2.6 support.
Support 2.7, 3.5-3.8, PyPy2/3.
Added tox for local testing.
[maurits] (#2)1.0.3 (2018-03-10)Bug fixes:Release it as a wheel as well as an egg.
[gforcada]1.0.2 (2016-11-01)New features:Test Python 3 compatibility.
[datakurre]1.0.1 - 2011-05-20Add license metadata.
[davisagli]1.0 - 2011-04-30No changes1.0b1 - 2009-03-30Initial release