Saravanan666/pypi-org huggingface dataset:
Package: repoze.lemonade
repoze.lemonade is a collection of utilties that make it possible to
create Zope CMF-like applications without requiring any particular
persistence mechanism.See docs/index.rst for more information.0.7.6 (2012-03-29)This release is the last which will maintain support for Python 2.4 /
Python 2.5.Added support for continuous integration usingtoxandjenkins.Added ‘setup.py dev’ alias (runssetup.py developplus installsnoseandcoverage).100% test coverage.Moved to GitHub.0.7.5 (2009/05/02)Speed up ‘get_content_type’ further by starting from context’s interfaces
(normally a much smaller set than all content types).0.7.4 (2009/01/28)Readd missingzope.testingdependency.Addtestingmodule.AddregisterContentFactoryAPI to testing module.AddregisterListItemAPI to testing module.0.7.3 (2008/12/28)Disuse theIContentTypeIInterface.  This feature requiresprovideInterface, which uses the global ZCML registry.  We are
able to mark our content interfaces usingIContentinstead.Added Sphinx docs.0.7.2 (2008/12/21)Make changes that allow us not to require “zope.security” (and its
dependencies).0.7.1 (2008/12/12)Speed upget_content_typeandget_content_typesby using a
content type cache rather than rooting through the adapter registry
every time we need to call them.  To invalidate the cache, dositemanager.unregisterUtility(IContentTypeCache).0.7 (2008/12/10)Addlemonade:listitemdirective andget_listitemsAPI.0.6 (2008/12/2)Usezope.component.getSiteManagerinstead ofzope.component.getGlobalSiteManagerto find an adapter registry.
This helps bfg inasmuch as it will use the bfg registry rather than
the base registry when getSiteManager has been hooked; it will fall
back to getting the global site manager if it has not been hooked.0.5 (2008/12/2)AddIContentinterface.  When anIFoointerface is declared
via ZCML aslemonade:content, add theIContentinterface to
the__bases__of theIFoointerface when the ZCML executes.Change howis_contentworks: use IContent.providedBy(object)
instead of scanning the application registry for factories.0.4 (unknown)Addis_contentandget_content_typeAPIs to content module.0.3 (2008/10/11)Evolution machinery moved torepoze.evolution.Workflow machinery moved torepoze.workflow.Folder machinery moved torepoze.folder.(Remaining: content registrations)0.2 (2008/10/05)Addedevolutionmodule; useful to evolve ZODB and other
persistent data structures in lockstep with code changes.  Needs
documentation.0.1Initial release.
Package: repoze.mailin
repoze.mailin READMEThis package provides a framework for mapping inbound e-mail onto
application-defined handlers.Please see docs/index.rst for the documentation.repoze.mailin Changelog0.4 (2012-01-25)Added an option to pass None to the the ‘pop’ method of the pending
queue:  in this case, the queue returnsallpending messsage IDs.Moved to GitHub.Ensure that thepollsterscript pushes message IDs onto the pending
queue, if configured.AddedSaneFilenameMaildir, which overrides the standard library’smailbox.Maildirto ensure that the generated filenames are strictly
sortable in creation order.0.3.1 (2009-07-08)N.B.:  the quarantine feature introduced in version 0.3 requires a
backward-incompatible change to the database scehma.  Existing databases
will not have the extra columns required to support the new feature.
The simplest fix is as follows:Stop any ongoing processing using the pending database.Dump any existing message IDs from the database.Move aside the database file.Rerun the script which creates the database file.Restore any dumped message IDs.0.3 (2009-07-08)Added quarantine to pending queue.0.2 (2009-06-23)100% unit test coverage.HardenedPendingQueue.popagainst RFC-violating message IDs with
non-decodable 8-bit characters.Added logging of underflows inPendingQueue.pop.MadePendingQueue.popa normal method, rather than a generator.AddedPendingQueue.loggerattribute:  if set, should obey the
interface of aloggingmodule logger.0.1.5 (2009-05-31)Skip incoming messages with duplicate message ids to messages we have
already processed;  apparently some Microsoft clients resend messages
without updating the Message-Id header, in violation of RFCs.0.1.4 (2009-05-04)Fixed case where pop with multiple pending IDs and a given isolation level
would cause the delete to fail with ‘database locked’.  See:https://bugs.launchpad.net/karl3/+bug/364251Fixed bug found by inspection where “underflow” on pop would leave the
message IDs whichhadbeen returned on the queue.0.1.3 (2009-03-13)AddedPendingQueue.__del__to ensure closing the SQL connection.MaildirStore.drainInbox:  don’t remove the message from the maildir
until after adding to the store.0.1.2 (2009-01-22)Madedrainoscript explicitly commit sqlite transactions if not running
indry-runmode.Addedisolation_levelargument toMaildirStore.__init__, to allow
control of how the queue commits transactions.  The default,None,
causes the connection to defer commits.0.1.1 (2009-01-16)Addedisolation_levelargument toPendingQueue.__init__, to allow
control of how the queue commits transactions.  The default,None,
causes the connection to autocommit after each statement.0.1 (2009-01-15)Initial release.
Package: repoze-oauth-plugin
repoze-oauth-plugin is arepoze.whoandrepoze.whatplugin implementing the
server side of theOAuth 1.0protocol. It supports both:2-legged flow where the client is at the same time a resource owner and3-legged flow where the client acts on behalf of a resource owner.You can read more about OAuth athueniverse.Installationeasy_install:$ <env>/bin/easy_install repoze-oauth-pluginpip:$ <env>/bin/pip install repoze-oauth-pluginDocumentationThe documentation can be found atpackages.python.org.SourceThe source code repository can be found atGitHub.
Package: repoze.obob
Overviewrepoze.obob is a reconstruction of the “bobo” precursor of Zope (the
“object publisher” portion), stripped down to be used as a possible
application endpoint in the ‘repoze’ stack.InstallationInstalling setuptoolsrepoze.obob depends on setuptools for its installation.  To install
setuptools:Download ez_setup.py fromhttp://peak.telecommunity.com/dist/ez_setup.pyRun ez_setup.py using Python 2.4.3 or better.  You can usehttp://peak.telecommunity.com/dist/virtual-python.pyif you’re
running a UNIX system to avoid polluting your “system” Python’s
“site-packages” directory with repoze-required eggs.Installing repozeAfter ez_setup.py is finished installing setuptools, run:$pyprefix/bin/python setup.py developThis will cause all packages required by repoze.obob to be
installed as Python eggs in the Python site-packages directory and
will cause the code from within the repoze.obob directory to be
used during execution.TestingTo all run repoze.obob tests, cd to the top-level repoze.obob
checkout dir and run:$pyprefix/bin/python setup.py test
Package: repoze.session
An HTTP sessioning system for web applications, based on code from thefasterhttp://agendaless.com/Members/tseaver/software/faster/Zope 2 product.repoze.sessionuses ZODB as its persistence
mechanism.See thedocssubdirectory orhttp://docs.repoze.org/session/for more documentation.repoze.session0.2100% test coverage.Changed index location.Pointed to docs in README.txt0.1Initial release.
Package: repoze.slicer
Introductionrepoze.sliceris a simple piece of WSGI middleware that can extract part of a
HTML response. This can be used to reduce the amount of parsing and
manipulation of DOM trees in browsers, which is especially expensive with older
versions of IE.Changelog1.0a2Handle CDATA correctly.
[wichert]Check multiple stackframes to deal with WSGIFilter versions.
[wichert]1.0a1first release
Package: repoze.squeeze
This package provides a WSGI middleware component which “squeezes”
HTML documents by merging browser resources (javascript
and stylesheets).It uses statistical analysis to determine the optimal bundles based on
the HTML documents that pass through it. Vary-headers are observed, as
are resource expiration dates.Documents that are not squeezed are given the ‘no-cache’ pragma in an
expectation that we will be able to squeeze it after sufficient
burn-in. Squeezed documents are served with expiration dates no later
than the expiration dates of the squeezed resources which it
references.UsageConfigure the middleware with the following two options (required):@cache_dir: Relative path to a directory where we store squeezed
resources@url_prefix: Path segment or full base URL that will be used to
serve the cache directory as static files.The following option is optional:@threshold: Floating-point parameter that controls the merge to
apperances threshold. This parameter can normally be left at the
default (0.5).In addition, you must configure the WSGI application to serve the file
cache directory from theurl_prefix(e.g. “cache”).InvalidationTo invalidate the file cache, upstream applications can set the
“X-Squeeze-Invalidate” header to a true value; note that before the
application is called, the middleware adds this key to the environment
such that applications which can’t modify the environment can still
flag for invalidation:>>> invalidate = environ["X-Squeeze-Invalidate"]
>>> invalidate()This will reset the file cache registry; note that no cache files are
ever deleted (to preserve web server integrity). You can manually
purge the file cache at any time be deleting the files (this is
allowed at run-time).Changelog0.4.4 (released 2009-06-22)Fixed edge-case where a response would not have a character set
defined and hence couldn’t be expressed as unicode. [malthe]Fixed edge-case with self-closing style elements. [malthe]Fixed edge-case issue with missing ttl-value. [malthe]0.4.3 (released 2009-05-11)Added environment variable control of file cache
invalidation. [malthe]0.4.2 (released 2009-05-11)Add semicolon after javascripts to make sure any function-block is
properly terminated (necessary due to concatenation). [malthe]0.4.1 (released 2009-04-20)Parse unicode body to ensure correct character decoding. [malthe]0.4 (released 2009-04-15)If a response has status ‘304 Not Modified’, update thettlbut
not the content. [malthe]If a script- or style-tag does not have a source or link, ignore
it. [malthe]Unquote request URL when querying cache. [malthe]Added support forrepoze.xmliterwhich allows reusing anlxmldocument tree between middlewares. [malthe]Media types for stylesheets are now taken into account when merging
the resources. Squeze uses CSS2@media <type>syntax. [jvloothuis]0.3 (released 2008-10-08)Relative URLs appearing in stylesheets are now made absolute before
merging. [malthe]0.2 (released 2008-10-03)Add setuptools as a dependency. [malthe]0.1 (released 2008-10-02)Initial release.
Package: repoze.urchin
repoze.urchin READMEThis package provides WSGI middleware for injecting the markup
required to use Google Analytics into web pages.Please see docs/index.rst for detailed documentation.repoze.urchin Changelog0.2 (2011-10-10)Replaced urchin javascript with new async tracking code. See:http://www.google.com/support/googleanalytics/bin/answer.py?answer=174090Note that the script is now inserted at the end of the <head> tag.Added bypass for HEAD requests. This is a workaround for an assertion in
webob.Response that doesn’t let you set the body on a response if the request
method is ‘HEAD’. This behavior on the part of webob is actually bogus, as
outlined here:http://blog.dscpl.com.au/2009/10/wsgi-issues-with-http-head-requests.htmlThe key issue here is that as long as anything in the WSGI stack tries to
special case ‘HEAD’ requests, we can end up with responses with headers which
differ depending on whether the request method is ‘GET’ or ‘HEAD’.  In this
specific example, by bypassing the urchin processing in the event of a HEAD
request, we wind up with a Content-Length header for HEAD that doesn’t
include the extra bytes for the inserted urchin code that we would get with a
GET request. This is, by definition of the standards, wrong, and yet
unavoidable as long as webob is in our stack.For now, we can hold our noses and know that probably nothing’s going to
really break because of this discrepency, but we can maybe try to convince
the webob crowd to drop conditional processing for HEAD requests.0.1 (2009-06-02)Initial release.
Package: repoze.urispace
repoze.urispaceREADMEOverviewrepoze.urispaceimplements theURISpace1.0 spec, as proposed
to the W3C by Akamai.  Its aim is to provide an implementation of
that language as a vehicle for asserting declarative metadata about a
resource based on pattern matching against its URI.Once asserted, such metadata can be used to guide the application in
serving the resource, with possible applciations including:Setting cache control headers.Selecting externally applied themes, e.g. inDeliverance.Restricting access, e.g. to emulate Zope’s “placeful security.”Please see thepackage docsfor detailed documentation.repoze.urispaceChangelog0.3.2 (2009-07-13)Fix rendering of PyPI page.0.3.1 (2009-07-13)100% unit test coverage.Added test / fix for bug inrepoze.urispace.middleware:make_middleware.Added support for coverage testing.0.3 (2009-07-06)Made thegetInfomethod of the middleware class into a separate API.0.2 (2009-07-04)Split out notes on the parser implementation from the main docs about
using the library / middleware.Added WSGI middleware which uses a URISpace to make assertions about the
current request’s URI, along with an API for extracting those assertions
from the environment.0.1 (2008-08-30)Initial release.
Package: repoze.vhm
Contents0.16 (2020-07-28)0.15 (2020-06-19)0.14 (2012-03-24)0.13 (2010-04-18)0.12 (2010-01-01)0.11 (2009-08-31)0.10 (2009-08-26)0.9 (2009-07-09)0.8 (2009-01-10)0.7 (2008-05-07)0.6 (2008-04-17)0.5 (2008-03-09)0.4 (2008-03-09)0.3 (2007-10-25)0.2 (2007-09-22)0.1 (2007-09-21)This package provides middleware and utilities for doing virtual
hosting within a WSGI/Repoze environment.  It is particularly useful
within arepoze.zope2environment, where it may be used as an
alternative to the classicVirtualHostMonster: method of doing
virtual hosting.Read the docs locally (seedocs/index.rst), or read themonline.
repoze.vhm Changelog
====================0.16 (2020-07-28)Add support for Python 3.7 and 3.8.Drop support for Python 3.3 and 3.4.0.15 (2020-06-19)Add support for testing on Travis.Drop support for Python 2.6.Add support fo Python 3.4, 3.5, and 3.6.0.14 (2012-03-24)Ensure HTTP_HOST is set correctly for non-standard ports under VHM paths.
This header requires a trailing port if not the default for a given service.
Seehttp://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23.
[davidjb]0.13 (2010-04-18)add conserve_path_infos for the VHMPathFilter middleware [kiorky]0.12 (2010-01-01)Update tests of middleware to check only thatmungeis called correctly.Testmungesepearately.100% test coverage.fixed xheaders filter to set PATH_INFO correctly
[vangheem]0.11 (2009-08-31)Add a repoze.vhm#vhm_explicit filter. This is like the vhm_xheaders
middleware, but the VHM host and/or root are set in the WSGI configuration
instead of in the request.Calculate a VIRTUAL_URL and put it into the environment. This is basically
the URL that the end user sees. repoze.zope2 >= 1.0.2 uses this to compute
the ACTUAL_URL request variable, for example.0.10 (2009-08-26)Apply the HTTP_HOST port number fix to the VHM Path filter as well.0.9 (2009-07-09)100% test coverage.HTTP_HOSTparameter now includes port number if nothttp:80orhttps:443.  Thanks to Martin Aspeli.0.8 (2009-01-10)Set ‘HTTP_HOST’ in environ to the same value as ‘SERVER_NAME’, FBO apps
which need it.0.7 (2008-05-07)Remove ‘dependency-links=’ to dist.repoze.org to prevent easy_install
from searching there inappropriately.0.6 (2008-04-17)Re-added the path-segment-based filter as an option, to support scenarios
in which the reverse proxy can be configured to rewrite the URL but not
to add headers.0.5 (2008-03-09)Brown bag release: I fudged the entry point for the xheaders filter.0.4 (2008-03-09)Kill off path-segment-based filter (repoze.vhm.zope2).  Only the
xheaders filter remains.Add license headers.The middleware now sets a ‘repoze.vhm.virtual_host_base’ which is
preferred by setServerUrl over ‘HTTP_HOST’ when present.Add a getVirtualRoot API.0.3 (2007-10-25)Fix setServerURL method to take into account HTTP_HOST passed by
client.0.2 (2007-09-22)Change repoze.vhm.zope2:setServerURL to allow Zope 2 to generate the
correct request[‘URL’] value when the vhm is in the pipeline.0.1 (2007-09-21)Initial release.
Package: repoze.vhm3
Contents0.15 (2018-02-14)0.14 (2012-03-24)0.13 (2010-04-18)0.12 (2010-01-01)0.11 (2009-08-31)0.10 (2009-08-26)0.9 (2009-07-09)0.8 (2009-01-10)0.7 (2008-05-07)0.6 (2008-04-17)0.5 (2008-03-09)0.4 (2008-03-09)0.3 (2007-10-25)0.2 (2007-09-22)0.1 (2007-09-21)This package provides middleware and utilities for doing virtual
hosting within a WSGI/Repoze environment.  It is particularly useful
within arepoze.zope2environment, where it may be used as an
alternative to the classicVirtualHostMonster: method of doing
virtual hosting.Read the docs locally (seedocs/index.rst), or read themonline.
repoze.vhm Changelog
====================0.15 (2018-02-14)Add support for testing on Travis.Drop support for Python 2.6.Add support fo Python 3.4, 3.5, and 3.6.0.14 (2012-03-24)Ensure HTTP_HOST is set correctly for non-standard ports under VHM paths.
This header requires a trailing port if not the default for a given service.
Seehttp://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23.
[davidjb]0.13 (2010-04-18)add conserve_path_infos for the VHMPathFilter middleware [kiorky]0.12 (2010-01-01)Update tests of middleware to check only thatmungeis called correctly.Testmungesepearately.100% test coverage.fixed xheaders filter to set PATH_INFO correctly
[vangheem]0.11 (2009-08-31)Add a repoze.vhm#vhm_explicit filter. This is like the vhm_xheaders
middleware, but the VHM host and/or root are set in the WSGI configuration
instead of in the request.Calculate a VIRTUAL_URL and put it into the environment. This is basically
the URL that the end user sees. repoze.zope2 >= 1.0.2 uses this to compute
the ACTUAL_URL request variable, for example.0.10 (2009-08-26)Apply the HTTP_HOST port number fix to the VHM Path filter as well.0.9 (2009-07-09)100% test coverage.HTTP_HOSTparameter now includes port number if nothttp:80orhttps:443.  Thanks to Martin Aspeli.0.8 (2009-01-10)Set ‘HTTP_HOST’ in environ to the same value as ‘SERVER_NAME’, FBO apps
which need it.0.7 (2008-05-07)Remove ‘dependency-links=’ to dist.repoze.org to prevent easy_install
from searching there inappropriately.0.6 (2008-04-17)Re-added the path-segment-based filter as an option, to support scenarios
in which the reverse proxy can be configured to rewrite the URL but not
to add headers.0.5 (2008-03-09)Brown bag release: I fudged the entry point for the xheaders filter.0.4 (2008-03-09)Kill off path-segment-based filter (repoze.vhm.zope2).  Only the
xheaders filter remains.Add license headers.The middleware now sets a ‘repoze.vhm.virtual_host_base’ which is
preferred by setServerUrl over ‘HTTP_HOST’ when present.Add a getVirtualRoot API.0.3 (2007-10-25)Fix setServerURL method to take into account HTTP_HOST passed by
client.0.2 (2007-09-22)Change repoze.vhm.zope2:setServerURL to allow Zope 2 to generate the
correct request[‘URL’] value when the vhm is in the pipeline.0.1 (2007-09-21)Initial release.
Package: repoze.what
**************************************************repoze.what -- Authorization for WSGI applications**************************************************:mod:`repoze.what` is an `authorization framework` for WSGI applications,based on :mod:`repoze.who` (which deals with `authentication` and`identification`).On the one hand, it enables an authorization system based on the groups towhich the `authenticated or anonymous` user belongs and the permissionsgranted to such groups by loading these groups and permissions into therequest on the way in to the downstream WSGI application.And on the other hand, it enables you to manage your groups and permissionsfrom the application itself or another program, under a backend-independentAPI. For example, it would be easy for you to switch from one back-end toanother, and even use this framework to migrate the data.This is just the authorization pattern it supports out-of-the-box, but youcan may it support other authorization patterns with your ownpredicates. It's highly extensible, so it's very unlikely that it will getin your way -- Among other things, you can extend it to check for manyconditions (such as checking that the user comes from a given country, basedon her IP address, for example).
Package: repoze.what.plugins.config
repoze.what.plugins.config – repoze.what with pasterconfigOverviewrepoze.what.plugins.configallows you to configurerepoze.whoandrepoze.whatusingpastedeploy. repoze.who and repoze.what are
WSGI middleware frameworks for authentication and authorization,
respectively.pasterandpastedeployallows you to configure your WSGI
application via INI files.Installing repoze.what.plugins.configYou can install repoze.what.plugins.config using git:git clone git://github.com/jdinuncio/repoze.what.plugins.config.git
cd repoze.what.plugins.config
python setup.py installUsing repoze.what.plugins.configrepoze.what.plugins.configoffers a config entry point for pastedeploy to
instantiate arepoze.who+repoze.whatmiddleware. You can use it
as a filter in the paster INI file:[filter:what]
use = egg:repoze.what.plugins.config#config
config_file = %(here)s/what.ini
who_config_file = %(here)s/who.iniThewhat.inifile has the same format of a who INI file, with the following
additions:You can define what plugins.There is a special sectionwhatwithgroup_adaptersandpermission_adaptersentries.You can combine who.ini and what.ini in one file. If you decide to do this,
remember that arepoze.whatmodprovider will be implicitly added to
yourrepoze.whoconfiguration.Example of useHere is a valid what.ini config file:[plugin:basicauth]
use = repoze.who.plugins.basicauth:make_plugin
realm = 'zbfg'

[plugin:htpasswd]
use = repoze.who.plugins.htpasswd:make_plugin
check_fn = repoze.who.plugins.htpasswd:plain_check
filename = %(here)s/passwd

[plugin:ini_group]
use = repoze.what.plugins.ini:INIGroupAdapter
filename = group.ini

[plugin:ini_permission]
use = repoze.what.plugins.ini:INIPermissionsAdapter
filename = permissions.ini

[general]
request_classifier = repoze.who.classifiers:default_request_classifier
challenge_decider = repoze.who.classifiers:default_challenge_decider
remote_user_key = REMOTE_USER

[identifiers]
plugins = basicauth

[authenticators]
plugins = htpasswd

[challengers]
plugins = basicauth

[what]
group_adapters = ini_group
permission_adapters = ini_permission
Package: repoze.what.plugins.hgwebdir
Contentsrepoze.what.plugins.hgwebdirChanges0.1.1 (2010-11-02)0.1.0 (2010-11-02)repoze.what.plugins.hgwebdirrepoze.what.plugins.hgwebdir is a repoze.what plugin suitable to be used
when serving Mercurial repositories through the wsgi application bundled
with Mercurial, hgwebdir.The basic advantage of using this plugin instead of hgwebdir authorization
mechanisms is that you can put all your authorization information for multiple
repositories in a single file. The format and purpose of this file is
inspired in the one that the mod_authz_svn Apache module uses. This plugin
makes a little bit easier to migrate from Subverion to Mercurial in
enterprise like environments.This plugin is distributed with the same license as repoze.what, e.g. a
BSD like license.Check thehttp://www.lorenzogil.com/projects/repoze.what.plugins.hgwebdir/website for the full documentation.Changes0.1.1 (2010-11-02)Add MANIFEST.in file. Fix an installation problem.0.1.0 (2010-11-02)Initial release