Saravanan666/pypi-org huggingface dataset:
Package: plone.login
Build Statusplone.loginA modernized drop-in replacement for the portal_skins-based login.InstallationInstall ploneconf.site by adding it to your buildout:[buildout]

...

eggs =
    plone.loginand then runningbin/buildout. Install it as usual in /prefs_install_products_formCompatibilityplone.loginis tested to work with Plone 5.1.
It should work with Plone 5.0 as well but is not yet tested.Customizing templatesThe templates for anyplone.logincan be customized because they’re simple browser-views.
Usez3c.jbotto apply your own overides.Customize where to redirect after loginYou can customize the location the user will be redirected to after successfuly logging in to the site.Just write an adapter as followsfromplone.login.interfacesimportIRedirectAfterLoginfromplone.login.interfacesimportIInitialLoginfromProducts.CMFPlone.utilsimportsafe_unicodefromzope.interfaceimportimplementerfromploneimportapi@implementer(IRedirectAfterLogin)classRedirectAfterLoginAdapter(object):def__init__(self,context,request):self.context=contextself.request=requestdef__call__(self,came_from=None,is_initial_login=False):if'Reviewer'inapi.user.get_roles():api.portal.show_message(u'Get to work!',self.request)came_from=self.context.portal_url()+'/@@full_review_list'else:user=api.user.get_current()fullname=safe_unicode(user.getProperty('fullname'))api.portal.show_message(u'Nice to see you again,{0}!'.format(fullname),self.request)ifnotcame_from:came_from=self.context.portal_url()returncame_fromThen register the adapter through ZCML:<adapter
    factory="your.addon.adapters.RedirectAfterLoginAdapter"
    for="OFS.interfaces.ITraversable
         zope.publisher.interfaces.IRequest"
    />As you can see, this adapter adapts context and request, so modify these according to your needs.The Plone Foundation, AuthorChangelog1.0rc1 (2018-06-18)Package created using templer
[The Plone Foundation]
Package: plone.mls.core
IntroductionPlone support for the Propertyshelf MLS.Changelog0.7.1 (2023-08-04)Add a new optional setting for an override email address which would be used as the sender for all inquiries.0.7 (2017-12-12)Add dependency to ps.plone.mls.Remove controlpanel settings from GS profiles (now handled by ps.plone.mls).0.6 (2017-08-21)Fix code-analysis errors and warnings.Update testing environment.Add Plone5 compatibility.I18N updates.0.5.4 (2014-07-14)I18N updates.0.5.3 (2014-04-23)Use request.parents to get the local context.0.5.2 (2014-04-23)Fixed context for local MLS settings (e.g. for collection settings).I18N updates.0.5.1 (2014-02-25)Fixed batching provider for Plone < 4.2.0.5 (2014-02-24)Added local MLS configuration.Added compatibility with deprecated batching used prior Plone 4.2.I18N updates.0.4.2 (2013-06-27)CI with travis-ci.0.4.1 (2013-06-26)Fixed Batching for Plone >= 4.2.I18N updates.0.4 (2012-02-11)Registered I18N locales folder.0.3 (2012-02-11)I18N updates merged.0.2 (2012-02-05)Replaced old PloneTestCase based tests with plone.app.testing.Added custom permission for controlpanel view.Added custom listing result batch provider based on plone’s batching.Added i18n support.0.1.1 (2011-10-26)Added error handling if connection to the MLS can’t be established.0.1 (2011-09-07)Use httplib2 instead of urllib2 to get json data.Use the new MLS listing api. Added language support.0.1b2 (2011-05-24)Fixed manage portlets fallback link (Plone 4 only).0.1b1 (2011-05-23)Now raises MLSConnectionErrors if no MLS connection or bad requests.Added manage portlets fallback link for dexterity types.0.1dev (2011-05-18)First Beta Release.
Package: plone.mockup
This is the integration package ofmockupfor Plone. Basically, it packagesmockupas a Python egg. For mockup itself, seehttps://github.com/plone/mockupThis package uses thegit submodulefeature. If you usebuildout.coredev,mr.developerwill make sure that the submodule is
checked out properly. If you do it manually, you can do one of the following:$ git clone git@github.com/plone/mockup.git --recursiveor:$ git clone git@github.com/plone/mockup.git
$ cd mockup
$ git submodule update --init --recursiveNotePlease, don’t develop mockup in here. git submodules are known to be
cumbersome in some circumstances. Do your mockup development directly in a
separate, dedicated mockup checkout.
Package: plone.oidc
Contentsplone.oidcFeaturesInstallationContributeSupportLicenseContributorsChangelog1.0.0a2 (2018-07-20)1.0.0a1 (2018-07-20)plone.oidcPureOpenID Connectimplementation for Plone framework which is 100% comply withOpenID Connect Core 1.0specifications. More over this product isHealth Relationship Trust Profile for OAuth 2.0complience with, so can be easily adaptable withHEARTecosystem.FeaturesDexterity Based Membrane user support.Fullly RESTFull API complience100% comply withHEARTecosystem.InstallationInstall plone.oidc by adding it to your buildout:[buildout]

...

eggs =
    plone.oidcand then runningbin/buildoutContributeIssue Tracker:https://github.com/nazrulworld/plone.oidc/issuesSource Code:https://github.com/nazrulworld/plone.oidcDocumentation:https://docs.plone.org/plone/oidcSupportIf you are having issues, please let us know.
We have a mailing list located at:email@gmail.comLicenseThe project is licensed under the GPLv2.ContributorsMd Nazrul Islam,email2nazrul@gmail.comChangelog1.0.0a2 (2018-07-20)plone.oidc.membrane.behaviors.IOidConnectClaimsbehavior is available.oidc_membrane_user_workflowworkflow is available.1.0.0a1 (2018-07-20)Initial release.
[nazrulworld]
Package: plone.pdfexport
plone.pdfexportProvides PDF export functionality for Plone content.FeaturesExports Documents, Event, News items and other custom content.Can be customized via CSS in the PDF Export control panel.Long tables which will be rendered on more than one page, will have the thead repeated on every page.One can use Plone body tag CSS classes to define CSS rules for specific Plone content.This add-on is based on the greatWeasyPrint library.TranslationsThis product has been translated intoenglishgermanInstallationInstall plone.pdfexport by adding it to your buildout:[buildout]

...

eggs =
    plone.pdfexportand then runningbin/buildoutNote: for Python 2 (Plone 5.1) you have to pin some packages:weasyprint = 0.42.3
cairocffi = 0.9.0
tinycss2 = 0.6.1
soupsieve = 1.9.6
cssselect2 = 0.2.2UsageAfter installing the add-on you can call the “aspdf” view on any Plone content.http://localhost:8080/Plone/news/aspdffor testing, you can add the GET parameter “html=1” to see the HTML version before it get rendered into a PDF.http://localhost:8080/Plone/news/aspdf?html=1We provide portrait and landscape mode with separate page setting for each mode:@page{margin:2.75cm1.4cm1.4cm1.4cm;size:landscape;@top-center{font-size:12px;color:#666666;content:"Beautiful Plone content, deserves a beautiful PDF export!";}@bottom-left{font-size:12px;color:#666666;content:"provided by derico.de";}@bottom-right{font-size:12px;color:#666666;content:"Page "counter(page);}}You can set which mode is the default. To use a different mode, you can add a request parameter:http://localhost:8080/Plone/front-page/aspdf?mode=landscape
http://localhost:8080/Plone/front-page/aspdf?mode=portaitAuthorsThis add-on was build byDerico[MrTango].ContributeIssue Tracker:https://github.com/plone/plone.pdfexport/issuesSource Code:https://github.com/plone/plone.pdfexportSupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsMaik Derstappen,md@derico.deChangelog2.1 (2022-11-04)fix python_requires definition
[MrTango]require Py >=3.7 and remove restapi down pinning
[MrTango]2.0 (2021-10-26)Provide both page mode’s (landscape and portrait) with a default setting and switch thru a request mode parameter
[MrTango]1.1 (2021-10-08)Improved image handling, now support also original images (without @@images/scales).[MrTango]1.0 (2021-10-06)Improve German translations
[MrTango]Improve error handling and add more tests
[MrTango]1.0b1 (2021-07-15)Resolve images internally in a custom WeasyPrint url_fetcher, this removes the need to resolves url’s for WeasyPrint, which was problematic with permissions or https cert issues
[MrTango]1.0a4 (2021-07-14)Don’t use  optimize_images=True in weasyprint for now, it only works in Py3 versions
[MrTango]1.0a3 (2021-07-14)Add print_image_scale to control panel and use custom image scale for PDF export
[MrTango]1.0a2 (2021-07-14)Fix missing lead image viewlet in PDF export
[MrTango]Merge content css classes with body tag classes instead of overriding them
[MrTango]1.0a1 (2021-07-13)Initial release.
[MrTango]
Package: plone.phonehome
OverviewThis package provides anonymous usage staticsticsA check-in call is made during Zope startup. If the list of installed packages
has changed since the previous check-in, that list of packages will be
submitted.InstallationTo installplone.phonehome, add it to theeggslist in yourbuildout.cfg. ZCML configuration will be automatically loaded via az3c.autoincludeentry point.QueryingThehttp://plonephonehome.appspot.comapplication provides aquerymethod which will return the number of reported instances using the providedpackageandversion. Aquerycall might look something like:http://plonephonehome.appspot.com/query?package=Products.CMFPlone&version=4.0CHANGES1.0a3 - 2011-05-21Don’t check in when running in Zope debug mode.
[esteele]1.0a2 - 2011-05-21Ignore ConflictErrors when adding the plonephonehomeid.
[esteele]1.0a1 - 2011-05-21Initial release
[esteele]
Package: plone.pony
Django’s got a pony now, so hey…Changelog1.2 - 2008-10-11Close the pre tag properly.
[davisagli]1.1 - 2008-10-08Don’t clobber other viewlets in plone.portalheader viewlet manager
[davisagli]Install pony to all themes.
[davisagli]1.0 - 2008-10-08Initial release
[witsch]
Package: plone.portlet.viewlet
IntroductionA portlet that displays a viewlet for Plone.Changelog0.4 - 2012-02-06Fix brown bag release.
[danjacka]0.3 - 2012-02-06Work with IViewView viewlets.
[danjacka]0.2 - 2010-04-16Fix edit form.
[elro]0.1 - 2010-04-09Initial release
[elro]
Package: plone.postpublicationhook
NoteThis package is provided for backwards compatibility. New code should use the
publication events introduced in Zope 2.12 directly.For Zope 2.10, a backport of the publication events is available inZPublisherEventsBackport. This is required for this package and may be added
to your buildout directly, or by specifying the ‘Zope2.10’ extra:eggs =
    Plone
    plone.postpublicationhook [Zope2.10]IntroductionThis package provides a hook into Zope’s ZPublisher that is run after the
publisher has completed publication, but before the the transaction is committed
and the response is returned to the requesting browser. This is practical for
caching purposes: it is the ideal place to determine and insert caching headers
into the response.Hooks usezope.event’s event mechanism using the
plone.validatehook.interfaces.IPostValidationEvent. This is based on the
standard ObjectEvent fromzope.component.ExampleAs an example we will write a bit of code which logs the path of every published
object. This is the code for the event handler:from zope.interface import Interface
from zope.component import adapter
from plone.postpublicationhook.interfaces import IAfterPublicationEvent
import logging

logger = logging.getLogger("LogRequest")

@adapter(Interface, IAfterPublicationEvent)
def LogRequest(object, event):
    if getattr(object, "getPhysicalPath", None) is None:
        path="Unknown path"
    else:
        path="/".join(object.getPhysicalPath()

    logger.info("Request for object %s" % path)To use this code you need to register it in zcml:<subscriber handler=".events.LogRequest" />Using ZPublisher events directlyThe IPubBeforeCommit event is equivalent to the IAfterPublicationEvent,
however it is not an ObjectEvent so there are a few changes:from zope.component import adapter
from ZPublisher.interfaces import IPubBeforeCommit
import logging

logger = logging.getLogger("LogRequest")

@adapter(IPubBeforeCommit)
def LogRequest(event):
    request = event.request
    object = request['PUBLISHED']
    if getattr(object, "getPhysicalPath", None) is None:
        path="Unknown path"
    else:
        path="/".join(object.getPhysicalPath()

    logger.info("Request for object %s" % path)Register it in zcml the same way:<subscriber handler=".events.LogRequest" />Changelog1.1 - 2010-06-08General and metadata cleanup.
[hannosch]Refactor to use ZPublisher publication events (available in Zope 2.10 with
ZPublisherEventsBackport.)
[lrowe]1.0rc1 - 2008-10-15Initial release
[wichert]
Package: plone.principalsource
IntroductionThis package provides a queriable sources (vocabularies) that return PAS
users, groups or principals (both users and groups).They are registered as named vocabularies, so you can do:class IMyInterface(Interface):
    users = schema.Choice(title=u"Users",
                          vocabulary="plone.principalsource.Users")

    groups = schema.Choice(title=u"Groups",
                           vocabulary="plone.principalsource.Groups")

    principals = schema.Choice(title=u"Principals",
                               vocabulary="plone.principalsource.Principals")The underlying source (see source.py) implements the IQuerySource interface
from z3c.formwidget.query. This means that it can be used for a query-select
widget, including the one in plone.formwidget.autocomplete.A note about unicodeThe source attempts to make it safe to do a __contains__ check, a getTerm()
lookup, and searches using unicode strings. This is somewhat constrained by
the underlying plugins. In particular, the standard ZODBGroups plugin is
incapable of searching for groups with unicode titles or ids, and returns
a list ofallgroups if passed a unicode string. As such, the source
forces all unicode strings used to search for groups to UTF-8 (searching for
users is unaffected).Also, remember that tokens should be 7-bit ASCII strings. getTermByToken() is
forgiving in that it silently encodes a unicode string to utf-8, but really
you should only pass unicode to this method.Changelog1.0 - 2013-06-04Fix compatibility with Plone 4.3.
[davisagli]1.0b1 - 2009-04-17Initial release
Package: plone.profileview
Plone Profile ViewThis package is designed to ease performace profiling of Plone websites.Normally, if you want to profile Plone you need to run Zope with profiling active. This results in extreme performance drops and no way to properly target a specific section or functionality (AFAIK).The product is a simple view that is made available only after installing the product through the site setup and available only to managers. This means that you can even run it in a production site, with no performace drops.How toThere are two views exposed:@@profileviewand@@profileview.ajax@@profileviewWill run profiling on the current context and download a pythoncProfiledump which you can load in the viewer of your choice.A target as well as arguments for the target can be specified via a get param (e.g.Plone/profileview?target=overview-controlpanel&kwargs={“a”=”b”})@@profileview.ajaxSimilar to@@profileviewexcept it saves the output profile dump in a temp file and exposes an interactive in-site interface to query the dumped file.A target as well as arguments for the target can be specified via hash params (e.g./Plone/profileview.ajax#?target=overview-controlpanel&kwargs={“a”=”b”})Depending on browser, you may need to refresh the page after changing the hash part of the URL.Installation[instance]
...
eggs =
    ...
    plone.profileviewChangelog0.2 - (2016-05-20)Cleanup: Remove profile in order not to leave traces within database
[avoinea]0.1 - (2016-05-12)Initial release
Package: plone.recipe.atcontenttypes
UsageThis recipe generates a custom ATContentTypes configuration file and places it in
the etc/ folder of your zope instance.You can use it with a part like this:[atcontenttypes-conf]
recipe                 = plone.recipe.atcontenttypes
zope-instance-location = /home/kevin/instance/Generally, we use this recipe in combination with a zope instance part. Here is
an example base onplone.recipe.zope2instance documentation[instance]
recipe         = plone.recipe.zope2instance
zope2-location = /path/to/zope2/install
user           = admin:admin
http-address   = 8080
eggs           = ${buildout:eggs} my.package
products       = ${buildout:directory}/products
zcml           = my.package

[atcontenttypes-conf]
recipe                 = plone.recipe.atcontenttypes
zope-instance-location = ${instance:location}
max-file-size          = ATImage:1mb
                         ATFile:100mb
                         ATNewsItem:500kb
max-image-dimension    = ATNewsItem:640,400
                         ATImage:2048,2048
pil-quality            = 95In case you have a multi-instance setup you can define multiple instance locations
and the recipe will create config files in each instance’s etc directory:[atcontenttypes-conf]
recipe                 = plone.recipe.atcontenttypes
zope-instance-location =
    ${instance1:location}
    ${instance2:location}Optionszope-instance-locationThe path(s) where your zope instance(s) is(are) installed. If you are also using the
plone.recipe.zope2instance recipe (like the second example above), and you
have that configured as a part called ‘instance’ prior to the atcontenttypes
part, you can use ${instance:location} for this parameter.max-file-size (default: no)This option let you set the maximum file size (in byte, kb or mb). You can
specify different file size limit, one for each content type.Example:max-file-size = ATImage:1mb
                ATFile:100mb
                ATNewsItem:500kbmax-image-dimension (default: 0,0)This option let you set the maximum image dimension (“w, h”). “0,0” means no
rescaling of the original image. This option is per-content-type and its
syntax is the same as above.Example:max-image-dimension = ATNewsItem:640,400
                      ATImage:2048,2048pil-quality (default: 90)This option affects the quality images get saved with.Reporting bugs or asking questionsWe have a shared bugtracker and help desk on Launchpad:https://bugs.launchpad.net/collective.buildout/Change History0.2.1 (2010-04-07)fix rest syntax of README to make it display nicely on pypi0.2 (2010-04-07)allow to set pil quality
[fRiSi]allow to supply multiple values to zope-instance-location
[fRiSi]0.1Initial implementation.
[kdeldycke]
Package: plone.recipe.bundlecheckout
plone.recipe.bundlecheckoutOptionsurlThe URL to check-out.subfolderOptionally specifies the name of an additional subfolder to be created.vcs-typeThe type of the source code repository. Defaults to svn for subversion.
Also supports cvs.nameOnly used and required for CVS. The name of the directory the code is
checked into.moduleOnly used and required for CVS. The name of the module to be checked out.cvsrootOnly used and required for CVS. The CVSROOT identifying the server.Reporting bugs or asking questionsWe have a shared bugtracker and help desk on Launchpad:https://bugs.launchpad.net/collective.buildout/Change History1.1Document the options, added README and CHANGES.
[hannosch]1.0First final release. Cleaned up setup.py.
[hannosch]0.2Added new optional subfolder option, which allows to specify a subfolder in
which to check out the bundle. This makes it possible to use this recipe for
normal packages as well, when specifying the package name with the subfolder
option.
[hannosch]0.1Initial implementation.
[hannosch]
Package: plone.recipe.command
IntroductionTheplone.recipe.commandbuildout recipe allows you to run a command
when a buildout part is installed or updated. It is very easy to use:[buildout]
parts = command

[command]
recipe = plone.recipe.command
command = cat README.txtThis configures a buildout part calledcommandwhich lists the contents
of README.txt when it is installed.ReferenceUnless otherwise specified all commands are run in the directory in which
buildout is invoked. Commands have to be present in the PATH or be specified
using an absolute pathname.The following options are supported:commandCommand to run when the buildout part is installed.update-commandCommand to run when the buildout part is updated. This happens when
buildout is run but the configuration for this buildout part has not
changed.locationA list of filesystem paths that buildout should consider as being managed
by this buildout part. These will be removed when buildout (re)installs
or removes this part.stop-on-errorWhenyes,onortrue, buildout will stop if the command ends
with a non zero exit code.Changes1.1 - 2010-02-25Addedstop-on-erroroption to stop buildout on non zero return code of
the command.
[fschulze]Use subprocess instead of os.system.
[fschulze]1.0 - 2007-09-14Initial release.
Package: plone.recipe.distros
plone.recipe.distrosOptionsurlsThe URLs of the archives to download. The archives specified in the same
part will be extracted into the same parts folder named after the part.
The full path to that folder will be available as ‘location’ from the
parts option dictionary.nested-packagesThe file names of one or more of the archives in the urls list.
This will cause only the Python packages (identified by a __init__.py) in
the top folder in the archive to be extracted into the destination.version-suffix-packagesThe file names of one or more of the archives in the urls list.
This will cause the part after the last dash to be omitted from the created
destination folder.Reporting bugs or asking questionsWe have a shared bugtracker and help desk on Launchpad:https://bugs.launchpad.net/collective.buildout/Changelog1.5 (2009-06-23)Create download-cache directory when not provided by buildout
[gotcha, jfroche]Simplified package metadata.
[hannosch]1.4 (2009-04-04)Added support for urls with http authentication.
[mond21]1.3Allow download-cache to fallback to download-directory if present.
[smcmahon]1.2Renamed download-directory to download-cache, which is the name that is used
by zc.buildout itself.
[hannosch]1.1Document the options, added README and CHANGES.
[hannosch]1.0First final release. Cleaned up setup.py.
[hannosch]0.3Handle nested packages where the packages are the top level folders as well.
This is needed for the PloneLDAP and ScriptableFields bundles.
[wichert]Better error handling. This prevents buildout from reporting an internal
error and informs the user what failed to download and why.
[wichert]0.2Make sure the directory exists even if the first package is a version suffix
or nested one :)
[optilude]0.1Initial implementation.
[hannosch]