Saravanan666/pypi-org huggingface dataset:
Package: collective.checkdocs
collective.checkdocs adds new distutils commandscheckdocsandshowdocsto validate restructured text in long_description field of Python eggs.
This package aims to make Python egg help page publishing and editing easier.Eggs’ long description field, which is usually also the README.txt file of the package, is reST formatted text. This text is converted
to HTML to show on the package page when package is published in distribution repositories like PyPI or plone.org.
Unfortunately, since repositories do poor job to validate incoming reST text, errors in the text will result to broken published
package pages.Unpublishing is usually very cumbersome.
We save our time by validating reST input usingcheckdocsandshowdocscommands
before submitting eggs to PyPi.InstallationInstall this to your development Python run-time:easy_install collective.checkdocsNote: On OSX at least Python version 2.5 or newer is required.New commandsThe following commands will be added to all setup.py installers.checkdocsRun long_description through reST to HTML converter and print errors and warnings to the standard output.Any errors or warnings will cause distutils to abort.Example:python setup.py checkdocs
<string>:4: (WARNING/2) Inline literal start-string without end-string.
error: long_description had reST syntax errorsshowdocsRun long_description through reST to HTML converter and display the result in a local web browser. Runs a web server in port 6969 until CTRL+C is pressed.Example:python setup.py showdocs
running showdocs
reST to HTML conversion available at at http://localhost:6969/ - press CTRL+C to interruptSource codehttps://svn.plone.org/svn/collective/collective.checkdocsAuthorsMikko OhtamaaResourceslong_description text isrestructured formatteddocutilsrstctl (inspiration and sources)How it all begun
Package: collective.check_munin
IntroductionThis is a reimplementation ofcheck_munin_rrd.plin Python.
It is used as a Nagios plugin command to read data collected from a Munin node by a Munin server.It usesrrdtooldirectly via “rrdtool lastupdate”.
rrdtool is a dependency for Munin servers, so it should be reliably available.Installation is typical for a Python package; virtualenv is recommended.Run the check_munin script for options.
Command-line options allow you to set domain, host, Munin-node plugin module, various include/exclude filters, and warning/critical ranges.
Options generally match check_munin_rrd.
Differences: -o option values may be globs; warning/critical specifications may be ranges, e.g., “-w 0:85” for warn when outside 0-85 range.Typical usage:check_munin -d dcn.org -H www.dcn.org -M df -o "_dev_*" -i _dev_shm -w 85 -c 95This reads the /var/lib/munin/dcn.org/www.dcn.org RRD files for the “df” module, including only RRD df files that match _dev_* and excluding _dev_shm:/var/lib/munin/dcn.org/www.dcn.org-df-_dev_*-g.rrdignoring /var/lib/munin/dcn.org/www.dcn.org-df-_dev_shm-g.rrdSample output:DF WARNING - /dev/sdi is 87.75 (greater than 85) | '/dev/sda1'=42.0611407378;85;95;0 '/dev/sdb'=31.7252599179;85;95;0 '/dev/sdh'=41.0162765108;85;95;0 '/dev/sdi'=87.7540702356;85;95;0 '/dev/sdj'=56.5373419066;85;95;0 '/dev/sdk'=54.4599777102;85;95;0Changelog1.0 (2013-09-03)Initial release
Package: collective.chromatable
IntroductionTo use it just follow this steps,Add collective.chromatable to your buildout eggsRun buildoutStart zopeInstall collective.chromatable into your Plone siteNow mark any scrollable table with chromatable class and you will get a nice scrolling table with fixed headersIf you want to change chromatable parameter don’t use the chromatable class, add the following lines to your template:<script>
jq(“#your_table_id”).chromatable({
width: “900px”,
height: “400px”,
scrolling: “yes”
});
</script>Changelog1.3.0Initial releaseBased on chromatable plugin version 1.3.0,http://www.chromaloop.com/posts/chromatable-jquery-plugin
Package: collective.cicero
Introductioncollective.ciceroprovides access toAzavea’sCicero APIfor performing
geography-based lookups of political data.  It is designed for integration with
Plone, but can be used in other contexts as well.UsageAccess to the API is provided via thecall_ciceromethod:call_cicero(service_name, method_name, *args, **kw)service_nameis one of theCicero web services. Currently the only
supported option is ‘ElectedOfficialQueryService’.method_nameis one of the SOAP methods supported by the chosen service.*argsand**kware the additional parameters required by the chosen
method.  See theCicero API documentationfor details.SettingsThe Cicero credentials (username and password) are looked up via aplone.registry-style IRegistry utility. In Plone, activating theplone.app.registrypackage followed bycollective.cicerowill set up a
suitable registry with the relevant settings available.Test ModeAtest modeis supported. In test mode, canned responses will be loaded from
disk instead of actually querying Cicero.Enable test mode by setting theCICERO_TESTenvironment variable. If this
variable is present in the operating system environment, test mode will be used.For test mode to work, the tests folder must contain a copy of the WSDL for the
service being tested, as well as a response file for the method being tested.
Responses can be obtained by running in normal mode with suds configured to log
at the debug level. A sample response for the GetOfficialsByAddress method of
the ElectedOfficialQueryService is included.Changelog1.1 (unreleased)Add a control panel for the Cicero settings, and make it validate the
credentials when they are saved.
[davisagli]Set the socket timeout to something more reasonable.
[davisagli]1.0 (2010-09-17)Initial release
Package: collective.civicrm
Table of ContentsLife, the Universe, and EverythingMostly HarmlessDon’t PanicInstallationBefore you beginUsageShare and EnjoyChangelog1.0a1 (2014-10-02)Life, the Universe, and EverythingCiviCRMis a web-based, open source, Constituent Relationship Management (CRM) software geared toward meeting the needs of non-profit and other civic-sector organizations.collective.civicrmis a package aimed to provide basic integration between Plone and CiviCRM.Mostly HarmlessDon’t PanicInstallationTo enable this package in a buildout-based installation:Edit your buildout.cfg and add add the following to it:[buildout]
...
eggs =
    collective.civicrmAfter updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.Check the box next tocollective.civicrmand click the ‘Activate’ button.NoteYou may have to empty your browser cache and save your resource registries in order to see the effects of the product installation.Before you beginTo use the CiviCRM integration you need the following information:REST interface URLSite keyEvery user that will interact with CiviCRM needs an API keySeeCiviCRM REST interface documentationfor more information on this.UsageAfter installing CiviCRM integration, go to the control panel configlet and set up the REST interface URL and site key.Set up the API key for all users that will use the CiviCRM integration.Go to the@@civicrm-find-contactsview at the site root and start making searches.
You can search for contacts by name or email, and you can filter the results by contact type, group and tag.You can select any contact from the results to see his details.
After a few seconds you will also see the relationships of the contact.You can also select any contact from the relationships list for more details.Share and Enjoycollective.civicrmwould not have been possible without the contribution of the following people:Héctor VelardePaul Munday (Python CiviCRM)You can find an updated list of package contributors onGitHub.Development sponsored byClean Clothes Campaign.ChangelogThere’s a frood who really knows where his towel is.1.0a1 (2014-10-02)Initial release.
Package: collective.ckeditortemplates
ContentsIntroductionExamplesInstallationTranslationsTests statusContributeLicenseContributorsChangelog0.9.1 (2023-11-28)0.9.0 (2023-05-23)0.3.3 (2021-04-20)0.3.2 (2015-10-06)0.3.1 (2015-02-09)0.3.0 (2015-01-15)0.2.4 (2014-11-05)0.2.3 (2014-06-06)0.2.2 (2014-05-23)0.2.1 (2014-04-18)0.2 (2014-03-31)0.1 (2014-03-10)IntroductionThis products create Plone templates forckeditorbased on thecollective.ckeditorpackage.ExamplesThis add-on can be seen in action at the following sites:https://docs.imio.be/imio-doc/ia.smartweb/https://docs.imio.be/imio-doc/ia.delib/https://docs.imio.be/imio-doc/ia.docs/InstallationInstall collective.ckeditortemplates by adding it to your buildout:[buildout]…eggs =collective.ckeditortemplatesand then running “bin/buildout”, next enable the product in your plone site.TranslationsThis product has been translated intoSpanish.French.Nederlands.You can contribute for any message missing or other new languages, join us atPlone Collective TeamintoTransifex.netservice with all world Plone translators community.Tests statusThis add-on is tested using Travis CI. The current status of the add-on is:ContributeIssue Tracker:https://github.com/collective/collective.ckeditortemplates/issuesSource Code:https://github.com/collective/collective.ckeditortemplatesDocumentation:https://pypi.org/project/collective.ckeditor/LicenseThe project is licensed under the GPLv2.ContributorsMartin Peeters, Original Author [Affinitic]Stephan Geulette, Original Author [IMIO]Benoit Suttor [IMIO]Leonardo J. Caballero G. [Plone Venezuela]Changelog0.9.1 (2023-11-28)Fixed bs4 version to have same behaviour in p4 and p6
[sgeulette]Updated setup
[sgeulette]0.9.0 (2023-05-23)Made compatible Plone 4.3 and Plone 6.0
[sgeulette]0.3.3 (2021-04-20)Add Transifex.net service integration to manage the translation process.
[macagua]Add Spanish translation
[macagua]Corrected bad import step requirement
[sgeulette]Added features param on BeautifulSoup init
[sgeulette]Degroked package
[sgeulette]Made the enabled state criteria a class variable, so it can be overrided.
[sgeulette]Sorted templates by title
[sgeulette]0.3.2 (2015-10-06)Member can see ckeditortemplates, so it possible to use local roles and adding a ckeditortemplate.
[bsuttor]Adding upgradesteps for workflow changes.
[bsuttor]0.3.1 (2015-02-09)Remove plone.multilingualbehavior because of to many bugs.0.3.0 (2015-01-15)Add plone.multilingualbehavior behavior, cktemplate is translable now.
[bsuttor]0.2.4 (2014-11-05)Move unindex ckeditorfolder to setup installation instead of upgrade step.
[bsuttor]0.2.3 (2014-06-06)Allow content type Image for cktemplatefolder/
[bsuttor]0.2.2 (2014-05-23)Add upgrade steps.
[bsuttor]0.2.1 (2014-04-18)Fix accents errors, decode content to utf-8.
[bsuttor]0.2 (2014-03-31)Remove the group restriction on CK Template
[mpeeters]Improve the parsing of html
[mpeeters]ckeditor template folder is no more allow globally, this container is
installed with package
[bsuttor]0.1 (2014-03-10)Initial release
[mpeeters, bsuttor]
Package: collective.classification.folder
collective.classification.folderAddon to manage classification foldersFeaturesFolders container typeFolder typeSubfolder typeTranslationsThis product has been translated intoFrenchInstallationInstall collective.classification.folder by adding it to your buildout:[buildout]

...

eggs =
    collective.classification.folderand then runningbin/buildoutContributeIssue Tracker:https://github.com/imio/collective.classification.folder/issuesSource Code:https://github.com/imio/collective.classification.folderSupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsMartin Peeters [original author]Stephan Geulette [Maintainer]Changelog1.1.1 (2024-02-26)Correctedon_will_moveto avoid error on delete.
[sgeulette]Removedcollective.z3cform.chosendependency.
[sgeulette]Removed folder rename restriction (now well handled in iconifiedcategory).
[sgeulette]Added INextPrevNotNavigable on folder classes (in zcml).
[sgeulette]1.1.0 (2024-02-19)Corrected tests.
[sgeulette]Corrected bug in indexer when the stored folders cannot be seen by the current user.
[sgeulette]Used imio.annex product so it is possible to add categorized annexe in folder and subfolder.
[sgeulette]Addedyesno_valueindex to store archived value and possibly use it in a faceted widget.
[sgeulette]Addedstate_filesizecolumn inFolderFacetedTableView.
[sgeulette]Removed fixed created sorting on IClassificationFacetedNavigable.
[sgeulette]Defined sort_index on subfolder column.
[sgeulette]Avoided folder rename
[sgeulette]1.0.2 (2023-11-28)Addedcollective.classification.folder.vocabularies:folder_portal_typesvocabulary to be used in faceted criteria.
[sgeulette]Added separate ClassificationFolder title and ClassificationSubfolder title columns.
[sgeulette]1.0.1 (2023-09-08)Removed python_requires causing problem to download from pypi.
[sgeulette]1.0.0 (2023-09-07)Set reallyclassification_categoriesfield on folders as not mandatory
[sgeulette]Settreating_groupsfield as required
[sgeulette]1.0a2 (2023-07-20)Setclassification_categoriesfield on folders as not required
[sgeulette]1.0a1 (2023-03-29)Initial release.
[mpeeters, sgeulette]Replaced collective.z3cform.chosen widget by collective.z3cform.select2.
Must remove “chosen” packages in next release.
[sgeulette]
Package: collective.classification.tree
collective.classification.treeTell 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.classification.tree by adding it to your buildout:[buildout]

...

eggs =
    collective.classification.treeand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.classification.tree/issuesSource Code:https://github.com/collective/collective.classification.treeDocumentation: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.ContributorsMartin Peeters [original author]Changelog1.0a3 (2023-09-08)Removed python_requires causing problem to download from pypi
[sgeulette]1.0a2 (2023-07-20)Corrected setup urls.
[sgeulette]1.0a1 (2023-03-29)Initial release.
[mpeeters]
Package: collective.cleanuprevisions
collective.cleanuprevisionsDelete content revisions (versions)FeaturesCan 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.cleanuprevisions by adding it to your buildout:[buildout]

...

eggs =
    collective.cleanuprevisionsand then runningbin/buildoutAuthorsProvided by awesome people ;)ContributorsPut your name here, you deserve it!?ContributeIssue Tracker:https://github.com/collective/collective.cleanuprevisions/issuesSource Code:https://github.com/collective/collective.cleanuprevisionsDocumentation: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.ContributorsMaik Derstappen,md@derico.deChangelog1.0a1 (2023-08-31)Initial release.
[MrTango]
Package: collective.clipboardupload
collective.clipboarduploadIntroductionQuintagroup has developed a collective.clipboardupload tool that essentially allows you to copy images and past them directly  into TinyMCE visual editor.CompatibilityPlone 4.0Plone 4.1Plone 4.3InstallationIn your buildout.cfg add the following:[buildout]
  ....

   eggs =
       ...
       collective.clipboarduploadYou don’t need to activate this add-on product after buildout installation. See the instance.log file to check whether Collective.clipboardupload was properly installed.UsageCollective.clipboarduploadis aPythonpackage, developed to simplify the  process of inserting images into visual editor without the need to upload the image.After you have installed the product, you can drag and drop picture from local folder, make print screen or select an area of image, opened in, for example, Paint, and copy it to the clipboard. Switch to Plone TinyMCE editor and Paste using your browser menu Edit -> Paste or key combination. The picture will be uploaded to the same folder, which contains an edited page, and stored as an image content type.
Title is automatically generated and can be changed any time. Furthermore, the path to the image itself upon saving in TinyMCE is rendered as resolveUID link.AuthorsMaksym ShalenyiChangelog0.1 (2013-07-30)first release
Package: collective.cloudfront
AWS CloudFront support for plone.app.cachingThis add-on watches for Purge notifications fromplone.app.cachingand sends the corresponding invalidation requests to an instance of Amazon’s CloudFront.FeaturesConfigurable in Site Setup (@@cloudfront-controlpanel)DocumentationYou will need to create an access key in your AWS Console.Once you have the key’s ID and secret, you can provide them to your Plone site via Site Setup under “CloudFront Configuration”. You will also need to provide the ID for your CloudFront distribution.InstallationInstall collective.cloudfront by adding it to your buildout:[buildout]

...

eggs =
    collective.cloudfrontand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.cloudfront/issuesSource Code:https://github.com/collective/collective.cloudfrontLicenseThe project is licensed under the GPLv2.ContributorsSix Feet Up,info@sixfeetup.comChangelog2.0 (2024-02-22)Drop python2 and Plone < 5.2 compatibility [erral]Fixes issue #2: remove includeDependecies [rber474]1.3 (2022-01-07)only run purging if add-on is installedcheck if purging is enabled in plone.app.caching
[abl123]Show the string representation of the exception
[skurfer]Set custom permissions for purging
[cdw9]1.2 (2021-05-14)add button for invalidating cache
[cdw9]1.0 (2017-07-17)Initial release.
[sixfeetup]
Package: collective.cmcicpaiement
IntroductionThis addon provide components to create the UI that will let you make a simple
paiement process to theCM CIC paiementsolutionIt can’t be use alone, you must provide custom implementation for
your contentsHow to installThis addon can be installed has any other addons. please follow officialdocumentationYou will find settings in the registry ( /portal_registry )ComponentsAller formThis addon add a base Browser to build an “Aller” form. The idea
is to adapt and implement the current context and request to be an order.An order must provide following elements:montant: the amount of the orderreference: the id of the orderYou can achieve this in many way: Having a cart done with simplecartjs
with an Order content type that will provide thoses information.
You will then just have to create the view inheriting from
collective.cmcicpaiement.aller.AllerForm , implements montant and reference
method and call aller_form in your template to render the paid button that
will do the job.RetourThis addon manage the “Retour” phase and response to the bank.
It use the zope event infrastructure to notify the system of paiements.The retour URL must be configured by the bank and must be:yoursite.com/@@cmcic_retourevent example:<subscriber
  for="collective.cmcicpaiement.retour.IRetourEvent"
  handler=".retour.retour_handler" />


def retour_handler(event):

    if event.code_retour == "Annulation":
        # Payment has been refused
        # The payment may be accepted later
        # put your code here (email sending / Database update)
        logger.info('paiement refused')

    elif event.code_retour == "payetest":
        # Payment has been accepeted on the test server
        # put your code here (email sending / Database update)
        logger.info('paiement accepted from test server')

    elif event.code_retour == "paiement":
        # Payment has been accepeted on the productive server
        # put your code here (email sending / Database update)
        logger.info('paiement accepted from production server')

    #*** ONLY FOR MULTIPART PAYMENT ***#
    elif event.code_retour == "paiement_pf2" or event.code_retour == "paiement_pf3" or event.code_retour == "paiement_pf4":
        # Payment has been accepted on the productive server for the part #N
        # return code is like paiement_pf[#N]
        # put your code here (email sending / Database update)
        # You have the amount of the payment part in event.montantech
        logger.info('paiement accepted from production server for a part')

    elif event.code_retour == "Annulation_pf2" or event.code_retour == "Annulation_pf3" or event.code_retour == "Annulation_pf4":
        # Payment has been refused on the productive server for the part #N
        # return code is like Annulation_pf[#N]
        # put your code here (email sending / Database update)
        # You have the amount of the payment part in event.montantech
        logger.info('paiement refused from production server for a part')CreditsPlanet Makina CorpusContact Makina-CorpusChangelog1.0b1 (2013-01-22)Initial release
Package: collective.cmfeditionsdexteritycompat
IntroductionThis package makesProducts.CMFEditionsworks withDexteritycontent types.In general CMFEditions works ok with Dexterity. The only problem is theversions_history_formtemplate: it does not show the older versions for Dexterity content items. Also, it may break if
the custom content type does not use the default view auto-generated by Dexterity.This package solve this problem by overridingversions_history_form.InstallationThe usual: add this package to the buildout and install the Generic Setup profile in the Plone Site.Extension/customization pointsTo make theversions_history_formtemplate work with Dexterity content types some views were
created. These can be overriden to customize the way older versions of a content type are displayed:@@download-version: Downloads an older version of a file stored in aplone.namedfilefield.@@content-core: Render only thecontent-corediv of the default view of a content item.@@version-view: Same as@@content-corebut makes links to file downloads use the@@download-versionview.Changelog0.1b8 (2012-09-17)Fixed failing test on Plone 4.1.6Changed requirement from Plone to Products.CMFPlone0.1b7 (2011-08-22)Synced template override with CMFEditions trunk.0.1b6 (2011-08-19)Removed import of Products.CMFEditions.setuphandlers.DEFAULT_POLICIES make it compatibile with
Products.CMFEditions >= 2.1.00.1b5 (2011-08-01)Do not extract the “content-core” div from the default view HTML code anymore in “@@content-core”.
Now we provide a default “@@content-core” based on the default views provided by Dexterity.0.1b4 (2011-08-01)Fixed bug: Unauthorized error when content type has custom view set up with Grok.0.1b3 (2011-07-20)Fixed tests again.0.1b2 (2011-07-13)Fixed tests.0.1b1 (2011-07-12)Initial release