Saravanan666/pypi-org huggingface dataset:
Package: repoze.bfg.formish
repoze.bfg.formishBindings for theformishform
generation library withrepoze.bfg,
including a set ofChameleontemplates that implement formish widget renderers.Please seehttp://docs.repoze.org/repoze.bfg.formishfor documentation.repoze.bfg.formish0.3 (2010-05-14)Made docs render.Add amethodattribute to theformZCML directive.  If set,
it must be one ofGETorPOST.  It is optional.  If it is
not provided,POSTis assumed.0.2 (2010-04-26)Make template renderer use utf-8 encoding by default.The following names are no longer available as attributes of the
request object in a form rendering:request.form_defaults
request.form_schema
request.form_fields
request.form_actions
request.form_widgets
request.form_action
request.form_controllerIt is now possible to render multiple forms per page using a<formish:forms>directive (see documentation).0.1 (2008-12-18)Initial release.
Package: repoze.bfg.htmlpage
This package provides a page-level rendering system for therepoze.bfgweb framework.It uses familiar technologies like HTML and CSS to dynamically use an
existing HTML document as template.Consult the documentation forchameleon.htmlfor information on
how to write templates.CreditsThis package was created by Malte Borch <mborch@gmail.com>, Stefan
Eletzhofer <stefan.eletzhofer@inquant.de> and Christof Haemmerle
<reco@nex9.com>.
Package: repoze.bfg.layouts
repoze.bfg.layoutsprovides a site layout story for therepoze.bfgframework. It uses familiar technologies like CSS3 to dynamically
inject dynamic content into static HTML.Consult the documentation forchameleon.htmlfor information on
how to write templates.CreditsThis package was created by Malte Borch <mborch@gmail.com>, Stefan
Eletzhofer <stefan.eletzhofer@inquant.de> and Christof Haemmerle
<reco@nex9.com>.
Package: repoze.bfg.restrequest
Introductionrepoze.bfg.restrequestimplements 4 additional Request types for use with
RESTful applications.Imagine you want to create separate views for one resource (identified by an URL) and different HTTP methods. In a default repoze.bfg project you can e.g. write:from repoze.bfg.restrequest import IGETRequest, IPOSTRequest
from webob import Response

def my_view_get(context, request):
    return Response("GET\n")

def my_view_post(context, request):
    return Response("POST "+request.body+"\n")This defines one methodmy_view_getin case aGETrequest is performed on this resource andmy_view_postin case aPOSTrequest is performed. You can do similar things withPUTorDELETE.In order to enable these views you need to wire them inconfigure.zcmllike this:<!-- include to activate the event handler for marking REST requests -->
<include package="repoze.bfg.restrequest" />

<bfg:view for=".models.IMyModel"
      request_type="repoze.bfg.restrequest.interfaces.IGETRequest"
      view=".views.my_view_get"
      />

<bfg:view for=".models.IMyModel"
      request_type="repoze.bfg.restrequest.interfaces.IPOSTRequest"
      view=".views.my_view_post"
      />You can do the same usingrepoze.bfg.conventionin which case your views would look like this:from repoze.bfg.restrequest import IGETRequest, IPOSTRequest
from webob import Response

@bfg_view(request_type=IGETRequest, for_=models.IMyModel)
def my_view_get(context, request):
    return Response("GET\n")

@bfg_view(request_type=IPOSTRequest, for_=models.IMyModel)
def my_view_post(context, request):
    return Response("POST "+request.body+"\n")Make sure you nevertheless includerepoze.bfg.restrequestin yourconfigure.zcml.Testing your applicationA simple test for the above would be to start your application and usecurlto see what the result is for different methods:$ curl http://127.0.0.1:6543/
GET

$ curl http://127.0.0.1:6543/ -d "posttest"
POST posttestChangelog1.0 - initial release (19 Oct 2008)Initial release1.0.1 - package bugfixingmoved HISTORY.txt to main directory so that setup.py finds and packages it.
Package: repoze.bfg.traversaladapter
An alternate implementation of therepoze.bfg.interfaces.ITraverserFactory(a “traverser”) which
allows you to register an adapter factory for the type or interface(s) of
objects encountered during traversal. This is a generalization of therepoze.bfg.traversalwrapperpackage which automatically wraps each
traversed object into a location-aware proxy.To enable this custom traverser factory, you need to add a dependency onrepoze.bfg.traversaladapterto your application and replace the default
traverser factory in theconfigure.zcmlconfiguration file like this:<adapter
    factory="repoze.bfg.traversaladapter.ModelGraphTraverser"
    provides="repoze.bfg.interfaces.ITraverserFactory"
    for="*"
    />Given a simple factory for adapters for a model classmymodule.Foodefined in the modulemymodulelike thisdef foo_factory(foo, parent, name):
    return FooAdapter(foo, parent, name)you could then registerfoo_factoryas a traversal adapter factory as
follows:<adapter
    factory="mymodule.foo_factory"
    provides="repoze.bfg.traversaladapter.ITraversalAdapterFactory"
    for="mymodule.Foo"
    />IfFoowas implementing the interfacemymodule.IFoo, the following
registration would also work:<adapter
    factory="mymodule.foo_factory"
    provides="repoze.bfg.traversaladapter.ITraversalAdapterFactory"
    for="mymodule.IFoo"
    />During traversal of yourrepoze.bfgapplication, each object of typeFoowill then automatically be wrapped in aFooAdapterinstance.Note that the registered factory always gets the current model object, its
parent and its name passed as arguments. If yourFooAdapterclass was set
up to receive aFooinstance, a parent object, and a name string in its
constructor like soclass FooAdapter(object):
    def __init__(self, foo, parent, name):
        self.foo = foo
        self.parent = parent
        self.name = nameyou could register the adapter class itself as the adapter factory.See therepoze.bfg.traversaladapter.tests.TraversalAdapterTestsmodule for further examples.
Package: repoze.bfg.traversalwrapper
repoze.bfg.traversalwrapperAn alternate implementation of therepoze.bfg.interfaces.ITraverserFactory(a “traverser”) which
wraps each traversed object in a proxy.  This allows a
“location-ignorant” model (a model which does not possess intrinsic__name__and__parent__attributes) to be used as the root
object and as any object returned from any other model’s__getitem__method during traversal.When this ITraverserFactory is registered as the traverser for arepoze.bfgapplication, during traversal, each object, including
the root object is wrapped in a proxy.  The proxy that provides the
traversed object with a__name__and__parent__attribute.
The__name__and__parent__attributes of the root proxy are
bothNone.  The__name__of subsequently traversed object is
the Unicode URL segment name which was used to look it up.  The__parent__of subsequently traversed objects is the previous
object traversed.In order to enable this package’s ITraverserFactory, register therepoze.bfg.traversalwrapper.ModelGraphTraverseras the traversal
policy, rather than the defaultModelGraphTraverser. To use this
feature, your application will need to have a dependency on this
package, as well as following stanza in itsconfigure.zcml:<adapter
    factory="repoze.bfg.traversalwrapper.ModelGraphTraverser"
    provides="repoze.bfg.interfaces.ITraverserFactory"
    for="*"
    />NoteWhen this ITraverserFactory is used, the intrinsic__name__or__parent__attribute of an object are ignored.
Even if an object in the graph (including the root objects) has an
intrinsic__name__and__parent__attribute, it will still
be wrapped in a proxy that override the object’s “real”__parent__and__name__attributes.repoze.bfg.traversalwrapper Changelog0.3 (2009-06-22)Compatibility with BFG 1.0a1.  This version is not guaranteed to be
compatible with any BFG version before 1.0a1.0.2 (2008-05-18)Use dictionary return values from our ITraverser in lockstep with
changes to 0.8dev.0.1Initial release (functionality moved out of BFG core).
Package: repoze.bfg.xmlrpc
repoze.bfg.xmlrpc READMEPlease see docs/index.rst for the documentation.repoze.bfg.xmlrpc Changelog0.4 (2010-06-11)Documentation tweaksAdd multi-method support via the XMLRPCView base class.0.3 (2009-07-06)Update docs to contain installation instructions.Change setup.cfg index to bfgsite.0.2 (2008-12-18)Add repoze.bfg.convention support.0.1 (2008-11-18)Initial release.
Package: repoze.browserid
repoze.browseridBrowser id middleware for WSGI.  Browser ids are cookies which
uniquely represent a user’s browser, for use by sessioning libraries.Seehttp://docs.repoze.org/browseridfor documentation.repoze.browserid0.3 (2010-04-26)Prevented deprecation warnings for import of the “sha” module under
2.6.Moved docs tohttp://docs.repoze.org/browserid(from README to Sphinx).0.2 (2010-01-14)Removed ‘ez_setup’ furniture:  setuptools is ubiquitous enough now.Silenced deprecation warning for import of ‘sha’ module under Python 2.6.100% test coverage.0.1 (2008-06-27)First release.
Package: repoze.component
repoze.component READMErepoze.componentis a package that software developers can use to
provide configurability and pluggability to their applications.repoze.componentprovides a generalized indirection mechanism
which can be used to provide plugin points to integrators or other
developers who may wish to provide alternate implementations of
application logic or configuration values.See docs/index.rst orhttp://docs.repoze.org/componentfor more information.repoze.component Changelog0.4 (2009-07-25)Make compatible with repoze.component 0.4.Addoverridekeys tocomponentandsubscriberdirectives.0.3 (2009-07-24)Update directive implementations to match newer repoze.component
calling conventions.Provide afullargument to theclearmethod ofrepoze.component.registry.Registrywhich clears the registry
entirely instead of just clearing unnamed registrations.  It
defaults to false.0.2 (2009-07-11)Break apart component type storage into__component_types__and__inherited_component_types__attributes.The__component_types__attribute has become a sequence of
component types stored directly on an instance as a result ofprovides(ob, 'sometype').The__inherited_component_types__attribute is stored on a class
as the result ofprovides(cls, 'sometype')( or via a
class-level call toprovides('a','b')).We then recompose these two separate attributes into a unified set
of component types when theresolvemethod of the registry is
called to create an effective list of component types.repoze.component.directlyprovidedbynow returns only the types
directly provided by an instance (its__component_types__);
previously it would also return the inherited component types
(because there was no such thing as an inherited component type).
However,repoze.component.providedbycontinues to return all
component types (both direct and inherited, as well as default
types).AddonlyprovidesAPI, which overwrites any existing__component_types__(or__inherited_component_types__)
attribute on the object.  It otherwise acts just likeprovides.0.1 (2009-06-22)Initial release.
Package: repoze.cssutils
repoze.cssutils===============``repoze.cssutils`` provides css parsing and utilities for CSS 2.1 and CSS3.1.0a6 (released 03/29/2009)- Fix bug that could lead to infinite recursion when a declarationis not terminated. Many thanks to Malthe Borche for reportingand providing fix.1.0a5 (released 02/10/2009)- Correct packaging error1.0a4 (released 01/09/2009)- Updated license and copyright info1.0a3 (released 12/29/2008)- Initial release
Package: repoze.dbbrowser
DB BrowserThis package provides a simple WSGI application to browse and edit
database tables. The application was developed using the repoze.bfg
web framework and uses the excellent JqueryUI library.After installing and configuring the application, you will be able
to browse and edit your application’s tables by visiting the
configured URL path. All the configuration that is needed is an
sqlalchemy database connection string for your database.InstallationInstall using setuptools, e.g. (within a virtualenv):$ easy_install repoze.dbbrowserConfiguration inside another repoze.bfg applicationThis package includes a repoze.bfg view callable, so that from another
repoze.bfg application, it is possible to configure it as a view. To do
so, simply add a view declaration inside your configure.zcml. Note
that your application’s settings must include the sqlalchemy database
connection string for your database, under the name ‘db_string’:<view
    view="repoze.dbbrowser.dbbrowser.app_view"
    name="dbbrowserapp"
/>The result of the application call will be turned into a webob Response
and returned to repoze.bfg as if the application was a view.Alternatively, this can be accomplished via Python when adding a view to
the repoze.bfg configurator:from repoze.dbbrowser.dbbrowser import app_view
config.add_view(app_view, name='dbbrowserapp')Configuration via PasteThe application can also be ‘mounted’ into another WSGI application
using Paste composite applications. Just choose a URL path for it and
add the corresponding section:[composite:main]
use = egg:Paste#urlmap
/ = myapp
/dbbrowser = dbbrowser

[app:myapp]
use = egg:myapp#app

[app:dbbrowser]
use = egg:repoze.dbbrowser#dbbrowser
db_string = sqlite:///%(here)s/myapp.db
theme_switcher = true
default_theme = redmondThe only required parameter is ‘db_string’, which is an sqlalchemy
database connection string.The ‘theme_switcher’ parameter is a boolean indicating if JQuery UI theme
switching functionality should be enabled.The ‘default_theme’ parameter is a string giving the name of the JQuery UI
theme to be used for the default dbbrowser UI. Keep in mind that JQuery
stores this id in a cookie, so you may have to clear cookies for this setting
to take effect if a previous theme was selected with the switcher.Reporting Bugs / Development VersionsVisithttp://bugs.repoze.orgto report bugs.  Visithttp://svn.repoze.orgto download development or tagged versions.Changelog0.1 (2010-03-02)Initial release.
Package: repoze.depinj
repoze.depinj READMEA dependency injection framework for unit testing.Please see docs/index.rst in the package orhttp://docs.repoze.org/depinjfor
the documentation.repoze.depinj Changelog0.3 (2011-03-07)Removed inaccurate statement in README.txt.0.2 (2011-03-07)Allow use of arbitrary (even unhashable) objects as lookup keys for
dependency injection.0.1 (2010-02-24)Initial release.
Package: repoze.dvselect
repoze.dvselect READMEThis package is a prototype of using :mod:repoze.urispaceto select
Deliverance themes and rules based on the URI of the request.Please see thepackage docsfor detailed documentation.repoze.dvselectChangelog0.1.2 (2009-07-11)Docs: fleshed out the example, including an annotatedURISpacefile and details on configuring the application via Python.Docs: remove spurious[filter:dvselect]section from the example
Paste INI file:  the middleware no longer requires configuration.Docs: point the user to the PyPI package docs page for detailed
documentation (makes a traversable link on the main PyPI page).0.1.1 (2009-07-10)Fix bug in the middleware entry point, which still required theurispaceargument, even though it didn’t need it.0.1 (2009-07-05)Initial release.The released version has a backward incompatibility with earlier SVN
versions of the pacakge:  the middleware no longer holds / applies
a privaterepoze.urispaceparser to the request URI;  instead, it
expects that therepoze.urispacemiddleware has already added
assertions to the environment based on the URI.
Package: repoze.errorlog
repoze.errorlogThis package implements aWSGImiddleware filter which intercepts exceptions and writes them to a Python
logging module channel (or thewsgi.errorsfilehandle, if no channel is
configured).  It also allows the browsing of limited exception history via
a browser UI.InstallationInstall using setuptools, e.g. (within a virtualenv):$ easy_install repoze.errorlogor using pip:$ pip install repoze.errorlogUsageFor details on using the various components, please see the
documentation indocs/index.rst.  A rendered version of that documentation
is also available online:http://repozeerrorlog.readthedocs.org/en/latest/Reporting BugsPlease report bugs in this package tohttps://github.com/repoze/repoze.errorlog/issuesObtaining Source CodeDownload development or tagged versions of the software by visiting:https://github.com/repoze/repoze.errorlogChangelog1.1 (2016-06-03)Add support for Python 3.5.Drop support for Python 2.6 and 3.2.1.0.0 (2015-02-07)Add support for Python 3.2, 3,3, and 3.4, and PyPy3.Drop dependency onPaste(forking / simplifyingpaste.request.parse_querystringandpaste.request.construct_url).Add support for testing on Travis.Add Sphinx documentation.Drop support for Python 2.4 / 2.5.0.9.2 (2012-03-29)This release is the last which will maintain support for Python 2.4 /
Python 2.5.Add support for continuous integration usingtoxandjenkins.Add support for PyPy.Add ‘setup.py dev’ alias (runssetup.py developplus installsnoseandcoverage).Moved to github.0.9.1 (2010-05-23)Make it possible to send exceptions to a logger channel as described
in the docs; this didn’t actually work previously because a) I’m not
very good at programming and b) the Python logging module is
terrible (usings[-1]and not catching an exception when the
string is empty rather than usings.endswith(), at least under
Python 2.4).0.9 (2010-05-23)Bump copyrights.Remove dependency onez_setup.py.Docs now show how to useErrorLogoutside PasteDeploy.Avoid a dependency onelementtreewhen used with Python 2.5 and later.
In those Python versions we used the built-inxml.etreesupport.100% test coverage.0.8 (2008-06-25)Remove post-mortem debug middleware (moved torepoze.debug).Initial PyPI release.0.7 (2008-05-21)Add post-mortem debug middleware (egg:repoze.errorlog#pdbpm)Remove versions from dependencies.0.6Get rid of find-link point tohttp://dist.repoze.orginsetup.py.Bumpez_setup.pyversion.0.5Depend onelementree1.2.6 explicitly.0.4Addignorefeature to configuration.  A value consisting of
space-separated entry point names can be used here, indicating that
these exception types should not be logged or kept in exception
history.Allow__error_log__view path to be configured viapathentry in
Paste configuration.Placerepoze.errorlog.pathandrepoze.errorlog.entryidin the
WSGI environment to allow error-catching middleware and apps to
compose URLs to errors.0.30.2 didn’t work as a filter. :-(Don’t usezope.pagetemplate, it has too many (potentially
conflicting) dependencies.  Instead usemeldfor template views.0.2Provide a TTW view (accessible via/__error_log__) of recent
tracebacks.0.1Initial release.
Package: repoze.evolution
repoze.evolutionREADMEPlease seedocs/index.rstfor further documentation.  The docs
are also available athttp://docs.repoze.org/evolution/repoze.evolutionChangelog0.6 (2013-05-20)Document / test compatibility with Python 3.2 / 3.3.0.5 (2013-04-25)Add support for building docs undertox.Addsetup.py docsalias (installs Sphinx and dependencies).Addsetup.py devalias (installs testing dependencies).Added support for continuous integration usingtoxandjenkins.Drop support for Python 2.4 / 2.5.0.4 (2011-01-13)ExtendedZODBEvolutionManagerto allow passing in a proxy for the
transaction module, or None (to suppress transactions altogether).Separated tests forZODBEvolutionManagerclass from those forevolve_to_latest.0.3 (2009-12-03)Remove unncessary assignment.repoze.evolutionno longer attempts to construe implicitly the version of
a database for which no version has been set explicitly.  Previously, an
unversioned database was construed to already be at the software version.
TheZODBEvolutionManagerperformed a write on read, setting the database
version to the software whenget_db_version()was called.  The
constructor forZODBEvolutionManagernow accepts an optional argument,initial_db_version, which specificies the version a database should be
considered to be if it does not already have a version set.  The default
value isNone.  If a database has not already been marked to be at a
particular version,get_db_version()will return the initial database
version value.  If this isNone, attempts to callevolve_to_latest()will fail with aValueError.  This represents a backwards incompatible
change, as databases for which no initial version is supplied explicitly will
now fail to evolve.Added new public method,set_db_version()to IEvolutionManager interface.0.2 (2009-06-25)100% test coverage.0.1 (2008-10-11)Initial release.
Package: repoze.filesafe
repoze.filesafeREADMErepoze.filesafe provides utilities methods to handle creation
of files on the filesystem safely by integrating with the ZODB package’s
transaction manager.  It can be used in combination with repoze.tm (or
repoze.tm2) for use in WSGI environments.Seedocs/index.rstfor documentation.Changelog2.2 - (2015-05-01)Add a newrepoze.filesafe.rename_filefunction to move files.Add additionalrecursiveparameter to allowrepoze.filesafe.rename_fileto useos.renames, i.e. recursively create/remove intermediate directories.2.1 - (2014-05-06)Fix OSError exceptions raised when deleting a non-existing file to have the
right errno value.2.0 - (2013-12-20)Update dummy datamanger to create BytesIO mock files if the file is
opened in binary mode.Update internal function naming to PEP8.2.0b2 (2013-03-20)Add support for Python 3.2 / 3.3.Note explicit support for Python 2.6 / 2.7.Drop support for Python < 2.6.2.0b1 (2011-08-31)Remove the need for a middleware. Instead the current transaction is
automatically joined if needed.
[wichert]PEP8.
[wichert]Restructure package to faciliate automated testing.
[wichert]1.1 (2011-01-13)Added deleteFile function/method.
[fschulze]1.0 (2010-06-29)Made DummyDataManager transaction aware.
[fschulze]1.0a6 (2009-12-09)Fix packaging error.
[wichert]1.0a5 (2009-12-09)Add a MockFile class to help with handling of files when using the
DummyDataManager.
[fschulze]1.0a4 (2009-11-12)Add a new openFile method to facilitate opening of files that have not been
commited yet.
[wichert]1.0a3 (2009-11-10)Add method to facilitate unit testing of code using repoze.filesafe.
[wichert]1.0a2 (2009-09-25)Add support for Python 2.4 and 2.5. [wichert]1.0a1 (2009-09-25)Initial Release
Package: repoze.filesafe-nfs
repoze.filesafeREADMErepoze.filesafe provides utilities methods to handle creation
of files on the filesystem safely by integrating with the ZODB package’s
transaction manager.  It can be used in combination with repoze.tm (or
repoze.tm2) for use in WSGI environments.Seedocs/index.rstfor documentation.Changelog2.0b3 (2013-07-25)support create file on NFS
[Eric Lo]2.0b2 (2013-03-20)Add support for Python 3.2 / 3.3.Note explicit support for Python 2.6 / 2.7.Drop support for Python < 2.6.2.0b1 (2011-08-31)Remove the need for a middleware. Instead the current transaction is
automatically joined if needed.
[wichert]PEP8.
[wichert]Restructure package to faciliate automated testing.
[wichert]1.1 (2011-01-13)Added deleteFile function/method.
[fschulze]1.0 (2010-06-29)Made DummyDataManager transaction aware.
[fschulze]1.0a6 (2009-12-09)Fix packaging error.
[wichert]1.0a5 (2009-12-09)Add a MockFile class to help with handling of files when using the
DummyDataManager.
[fschulze]1.0a4 (2009-11-12)Add a new openFile method to facilitate opening of files that have not been
commited yet.
[wichert]1.0a3 (2009-11-10)Add method to facilitate unit testing of code using repoze.filesafe.
[wichert]1.0a2 (2009-09-25)Add support for Python 2.4 and 2.5. [wichert]1.0a1 (2009-09-25)Initial Release