Saravanan666/pypi-org huggingface dataset:
Package: zope.dottedname
zope.dottednameResolve strings containing dotted names into the appropriate python object.Changes6.0 (2023-03-27)Add support for Python 3.11.Drop support for Python 3.6.5.0 (2022-09-08)Add support for Python 3.8, 3.9, 3.10.Drop support for Python 2.7, 3.4, 3.5.4.3 (2018-10-05)Add support for Python 3.7.Drop support for Python 3.3.4.2 (2017-05-11)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.2.100% unit test coverage (including branches).Convert doctests to Sphinx documentation, including building docs
and running doctest snippets undertox.4.1.0 (2014-12-26)Add support for PyPy3.Add support for Python 3.4.Add support for testing on Travis.4.0.0 (2013-02-05)Made tests pass on Python 3.2, 3.3 and PyPy.Add support for continuous integration usingtox.3.4.6 (2009-09-15)Make tests pass on python26.3.4.5 (2009-01-27)Move README.txt in the egg, so tests works with the released egg as well.3.4.4 (2009-01-27)Fix ReST in README.txt, fix broken tests with recent zope.testing.3.4.3 (2008-12-02)More documentation and tests.3.4.2 (2007-10-02)Fix broken release.3.4.1 (2007-10-02)Update package meta-data.3.4.0 (2007-07-19)Initial Zope-independent release.
Package: zope.error
zope.errorThis package provides an error reporting utility which is able to store errors.Changes5.0 (2023-07-06)Add support for Python 3.11.Drop support for Python 2.7, 3.5, 3.6.4.6 (2022-08-29)Add support for Python 3.8, 3.9, 3.10.Drop support for Python 3.4.4.5.0 (2018-10-19)Add support for Python 3.7.4.4.0 (2017-07-22)Drop support for Python 3.3.Add support for Python 3.6.100% test coverage.Remove internal_compatmodule in favor ofsix, which we
already had a dependency on.Stop decoding in ASCII (whatever the default codec is) in favor of UTF-8.Tighten the interface ofILocalErrorReportingUtility.setProperties. Nowignored_exceptionsis required to be str or byte objects.
Previously any object that could be converted into a text object via
the text constructor was accepted, but this encouraged passing class
objects, when in actuality we need the classname.Stop ignoringKeyboardInterruptexceptions and other similarBaseExceptionexceptions during theraisingmethod.4.3.0 (2016-07-07)Add support for Python 3.5.Drop support for Python 2.6.bugfix: fix leak by convertingrequest.URLto string inErrorReportingUtility4.2.0 (2014-12-27)Add support for PyPy and PyPy3.Add support for Python 3.4.4.1.1 (2014-12-22)Enable testing on Travis.4.1.0 (2013-02-21)Add compatibility with Python 3.34.0.0 (2012-12-10)Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.Sort request items for presentation in the error reporting utility.Don’t HTML-escape HTML tracebacks twice.3.7.4 (2012-02-01)Add explicit tests for escaping introduced in 3.7.3.Handing names of classes those string representation cannot
be determined as untrusted input thus escaping them in error reports.Fix tests on Python 2.4 and 2.5.3.7.3 (2012-01-17)Escape untrusted input before constructing HTML for error reporting.3.7.2 (2010-10-30)Setcopy_to_zlogby default to 1/True.
Having it turned off is a small problem, because fatal (startup) errors
will not get logged anywhere.3.7.1 (2010-09-25)Add test extra to declare test dependency onzope.testing.3.7.0 (2009-09-29)Clean up dependencies. Droped all testing dependencies as we only need
zope.testing now.Fix ImportError when zope.testing is not available for some reason.Remove zcml slug and old zpkg-related files.Remove word “version” from changelog entries.Change package’s mailing list address to zope-dev at zope.org as
zope3-dev at zope.org is now retired. Also changedcheeseshoptopypiin the package’s homepage url.Add dependency on ZODB3 as we use Persistent.Use a mock request for testing. Dropped the dependency on zope.publisher
which was really only a testing dependency.Reduce the dependency on zope.container to one on zope.location by no
longer using the Contained mix-in class.3.6.0 (2009-01-31)Use zope.container instead of zope.app.containerMove error log bootstrapping logic (which was untested) tozope.app.appsetup, to which we added a test.3.5.1 (2007-09-27)Rebump to replace faulty egg3.5.0Initial documented releaseMoved core components fromzope.app.errorto this package.
Package: zope.errorview
zope.errorviewProvides basic HTTP and Browser views for common exceptions.Refactored fromzope.app.http.exception andzope.app.exception.CHANGES2.0 (2023-02-09)Drop support for Python 2.7, 3.4, 3.5, 3.6.Add support for Python 3.7, 3.8, 3.9, 3.10, 3.11.1.2.0 (2018-01-15)Remove the whitespace between the content-type and charset of the default
error views. This is because in certain cases zope.publisher.http will parse
the content type parameters and combine them back again without the
whitespace. This fix makes things more predictable esp. in tests.1.1 (2018-01-10)Additional fixes for Python 3 compatibility.NOTE: The error view base classes now set a Content-Type response header to
“text/plain”. If your error view subclassing from the zope.errorview classes
return a response body other than “text/plain” you need to explicitly set
the Content-Type in your views.1.0.0 (2017-05-10)Add support for Python 3.4, 3.5, 3.6 and PyPy.Fix typo in Dutch translation0.11 (2011-06-28)Added nl translations.0.10 (2011-02-08)Exception views do not by default provide ISystemErrorView anymore as it
would result in duplicate log output. The mixin class still exists for
writing custom error views that do provide ISystemErrorView.0.9 (2011-01-20)Initial release.
Package: zope.event
zope.eventREADMEThezope.eventpackage provides a simple event system, including:An event publishing API, intended for use by applications which are
unaware of any subscribers to their events.A very simple synchronous event-dispatching system, on which more sophisticated
event dispatching systems can be built. For example, a type-based
event dispatching system that builds onzope.eventcan be found inzope.component.Please seehttp://zopeevent.readthedocs.io/for the documentation.zope.eventChangelog5.0 (2023-06-23)Drop support for Python 2.7, 3.5, 3.6.4.6 (2022-12-15)Port documentation to Python 3.Add support for Python 3.10, 3.11.4.5.0 (2020-09-18)Add support for Python 3.8 and 3.9.Remove support for Python 3.4.4.4 (2018-10-05)Add support for Python 3.74.3.0 (2017-07-25)Add support for Python 3.6.Drop support for Python 3.3.4.2.0 (2016-02-17)Add support for Python 3.5.Drop support for Python 2.6 and 3.2.4.1.0 (2015-10-18)Require 100% branch (as well as statement) coverage.Add a simple class-based handler implementation.4.0.3 (2014-03-19)Add support for Python 3.4.Updateboostrap.pyto version 2.2.4.0.2 (2012-12-31)Flesh out PyPI Trove classifiers.Add support for jython 2.7.4.0.1 (2012-11-21)Add support for Python 3.3.4.0.0 (2012-05-16)Automate build of Sphinx HTML docs and running doctest snippets via tox.Drop explicit support for Python 2.4 / 2.5 / 3.1.Add support for PyPy.3.5.2 (2012-03-30)This release is the last which will maintain support for Python 2.4 /
Python 2.5.Add support for continuous integration usingtoxandjenkins.Add ‘setup.py dev’ alias (runssetup.py developplus installsnoseandcoverage).Add ‘setup.py docs’ alias (installsSphinxand dependencies).3.5.1 (2011-08-04)Add Sphinx documentation.3.5.0 (2010-05-01)Add change log tolong-description.Add support for Python 3.x.3.4.1 (2009-03-03)A few minor cleanups.3.4.0 (2007-07-14)Initial release as a separate project.
Package: zope.filerepresentation
zope.filerepresentationThe interfaces defined here are used for file-system and file-system-like
representations of objects, such as file-system synchronization, FTP, PUT, and
WebDAV.Documentation is hosted athttps://zopefilerepresentation.readthedocs.io/Changes6.0 (2023-01-14)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.9, 3.10, 3.11.5.0.0 (2020-03-31)Drop support for Python 3.4.Add support for Python 3.7 and 3.8.Ensure all objects have a consistent interface resolution order.
Seeissue 7.4.2.0 (2017-08-10)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.4.1.0 (2014-12-27)Add support for PyPy3.Add support for Python 3.4.4.0.2 (2013-03-08)Add Trove classifiers indicating CPython and PyPy support.4.0.1 (2013-02-11)Add tox.ini to release.4.0.0 (2013-02-11)Add support for Python 3.3 and PyPy.Drop support for Python 2.4 / 2.5.3.6.1 (2011-11-29)Add undeclaredzope.schemadependency.Removezope.testingtest dependency andtestextra.3.6.0 (2009-10-08)AddIRawReadFileandIRawWriteFileinterfaces. These extendIReadFileandIWritefile, respectively, to behave pretty much like a
standard Python file object with a few embellishments. This in turn allows
efficient, iterator- based implementations of file reading and writing.Remove dependency onzope.container:IReadDirectoryandIWriteDirectoryinherit only from interfaces defined inzope.interfaceandzope.interface.common.mapping.3.5.0 (2009-01-31)Change use ofzope.app.containertozope.container.3.4.0 (2007-10-02)Initial Zope-independent release.
Package: zope.fixers
IntroductionFixers for Zope Component Architecture and the frameworks built with it.Currently, there is only one fixer, fix_implements. This fixer will change
all uses of implements(IFoo) in a class body to the class decorator
@implementer(IFoo), which is the most likely Python 3 syntax for
zope.interfaces implements statements.UsageTypically you will use zope.fixers together with Distribute’s 2to3 support.
This is done by adding zope.fixers to some parameters in setup():>>> setup(
...     install_requires = ['zope.fixers'],
...     use_2to3 = True,
...     use_2to3_fixers = ['zope.fixers'],
... )For an example usage of a complex case, look at:http://svn.zope.org/zope.interface/branches/regebro-python3/setup.py?rev=106216&view=markupThat setup.py supports both distutils, setuptools and distribute, all versions
of python from 2.4 to 3.1, and has an optional C-extension, so don’t worry if
it’s overwhelming. For simple projects all you need is to use Distribute and
add the above three lines to the setup.py. Distribute has more documentation
on how to use it to support Python 3 porting.If you don’t want to use Distribute things get a bit more complex, as you have
to make the list of fixers yourself and call lib2to3 with that:>>> from lib2to3.refactor import RefactoringTool, get_fixers_from_package
>>> fixers = get_fixers_from_package('lib2to3.fixes') + \
...          get_fixers_from_package('zope.fixers')And the run the fixing with the fixers:>>> tool = RefactoringTool(fixers)
>>> tool.refactor(files, write=True)Fixer ScriptThe package also provides a console script calledzope-2to3that has the
same arguments as2to3but applies the fixers defined in this package.CHANGES1.1.2 (2013-02-23)Removed setup.cfg and make sure that we point to real Change Log.1.1.1 (2013-02-23)Remove support for Python 2.7 again. It did not work.1.1.0 (2013-02-22)Added console scriptzope-2to3.1.0.0 (2009-09-12)Initial release. Includes the implements fix to change implements(IFoo)
class body call to@implementer(IFoo)class decorator.
Package: zope_fixtures
Copyright (c) 2011, Robert Collins <robertc@robertcollins.net>Licensed under either the Apache License, Version 2.0 or the BSD 3-clause
license at the users choice. A copy of both licenses are available in the
project source as Apache-2.0 and BSD. You may not use this file except in
compliance with one of these two licences.Unless required by applicable law or agreed to in writing, software
distributed under these licenses is distributed on an “AS IS” BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  See the
license you chose for the specific language governing permissions and
limitations under that license.Zope fixtures provides Fixtures (http://pypi.python.org/pypi/fixtures) for
use with Zope tests. These permit easy unit testing in Zope environments.DependenciesPython 2.4+
This is the base language fixtures is written in and for.zope.interfaces.Fixtures (http://pypi.python.org/pypi/fixtures).For use in a unit test suite using the included glue, one of:Python 2.7unittest2bzrlib.testsOr any other test environment that supports TestCase.addCleanup.Writing your own glue code is easy, or you can simply use the fixtures directly
without any support code.To run the test suite for zope_fixtures, testtools is needed.See the Fixtures documentation for overview and design information.Stock FixturesComponentsFixtureThis permits overlaying registrations in the zope registry. While the fixture
is setup any registrations made are local to the fixture, and will be thrown
away when the fixture is torn down.>>> from zope_fixtures import ComponentsFixture
>>> from zope.interface import Interface, implements
>>> from zope.component import getSiteManager
>>> class ITestUtility(Interface):pass
>>> class TestUtility(object):
...     implements(ITestUtility)
>>> with ComponentsFixture():
...     getSiteManager().registerUtility(TestUtility())UtilityFixtureThis permits simple replacement of a single utility.>>> from zope_fixtures import UtilityFixture
>>> with UtilityFixture(TestUtility()):
...     pass
Package: zope.generations
zope.generationsGenerations are a way of updating objects in the database when the application
schema changes.  An application schema is essentially the structure of data,
the structure of classes in the case of ZODB or the table descriptions in the
case of a relational database.Seehttps://zopegenerations.readthedocs.io/for complete documentation.CHANGES5.1.0 (2022-02-11)Drop support for Python 3.4.Add support for Python 3.8, 3.9 and 3.10.5.0.0 (2019-09-23)Add support for transaction managers operating in explicit mode.
Schema managers were previously required not to commit transactions
in theirevolveorinstallmethods, but a loophole was open
to allow them to commit “if there were no subsequent operations”.
That loophole is now closed, at least in explicit mode. Seeissue 8.4.1.0 (2018-10-23)Add support for Python 3.7.4.0.0 (2017-07-20)Dropped support for Python 2.6 and 3.3.Added support for Python 3.4, 3.5, 3.6, PyPy2 and PyPy3.4.0.0a1 (2013-02-25)Added support for Python 3.3.Replaced deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Dropped support for Python 2.4 and 2.5.3.7.1 (2011-12-22)Removed buildout part which was used during development but does not
compile on Windows.Generation scripts add a transaction note.3.7.0 (2010-09-18)Initial release extracted fromzope.app.generations.Generations key (stored in database root) has been changed fromzope.app.generationstozope.generations.  Migration is done whenevolveis run the first time by coping the existing generations data
over to the new key. So the old and the new key can be used in parallel.
Package: zope.globalrequest
IntroductionThis package provides a contextless way to retrieve the currently active request object in a zope-based web framework.
To do so you simply need to do the following:from zope.globalrequest import getRequest
request = getRequest()This package is mainly intended to be used with the Zope/Plone stack.
While it also works with the Zope3 framework,
the latter promotes a clean separation of concerns and the pattern of having a globally available request object is discouraged.Changelog2.0 (2023-03-27)Drop support for Python 2.7, 3.5, 3.6.Mention Python 3.11 support in trove classifiers.1.6 (2022-10-18)Add support for Python 3.8, 3.9, 3.10 and 3.11Drop support for Python 3.4.1.5 (2018-10-04)Add support for Python 3.7.1.4 (2017-05-29)Turn functional tests into better covering unit tests and also add more tests.
This removes test dependencies on unrelated packages.1.3 (2016-10-22)Python 3 compatibility.1.2 (2016-06-07)Lighten test dependencies by using neitherzope.app.testingnorzope.app.zcmlfilesany longer.1.1 (2015-04-29)Fix import locations and declare all dependencies.
[thet]1.0 (2010-08-07)Fix test setup regardingzope.securitypolicy.
[ldr]1.0a2 (2009-01-17)Update documentation to clarify the intentions of this package.  Also seehttp://thread.gmane.org/gmane.comp.web.zope.devel/18023for more information.
[witsch]1.0a1 (2009-01-15)Initial release
[witsch]
Package: zope.hookable
zope.hookableThis package supports the efficient creation of “hookable” objects, which
are callable objects that are meant to be optionally replaced.The idea is that you create a function that does some default thing and make it
hookable. Later, someone can modify what it does by calling its sethook method
and changing its implementation.  All users of the function, including those
that imported it, will see the change.Documentation is hosted athttps://zopehookable.readthedocs.ioChanges6.0 (2023-10-05)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.12.5.4 (2022-11-17)Add support for building arm64 wheels on macOS.5.3 (2022-11-03)Add support for the final release of Python 3.11.5.2 (2022-09-13)Add support for Python 3.10 and 3.11 (as of 3.11.0rc1).Disable unsafe math optimizations in C code.  Seepull request 25.5.1.0 (2021-07-20)Add support for Python 3.9.Create Linux aarch64 wheels.5.0.1 (2020-03-10)Stop using the setuptoolsFeatureclass, allowing this
project to be built from source with newer versions of setuptools
that remove that functionality.5.0.0 (2019-11-12)Add support for Python 3.7 and 3.8.Drop support for Python 3.4.4.2.0 (2017-11-07)Expose the__doc__(and, where applicable,__bases__and__dict__) of the hooked object. This lets Sphinx document them.
Seeissue 6.RespectPURE_PYTHONat runtime. At build time, always try to
build the C extensions on supported platforms, but allow it to fail.
Seeissue 7.4.1.0 (2017-07-26)Drop support for Python 2.6, 3.2 and 3.3.Add support for Python 3.5 and 3.6.4.0.4 (2014-03-19)Add support for Python 3.4.4.0.3 (2014-03-17)Updateboostrap.pyto version 2.2.Fix extension compilation on Py3k.4.0.2 (2012-12-31)Flesh out PyPI Trove classifiers.4.0.1 (2012-11-21)Add support for Python 3.3.Avoid building the C extension explicitly (use the “feature” indirection
instead).https://bugs.launchpad.net/zope.hookable/+bug/10254704.0.0 (2012-06-04)Add support for PyPy.Add support for continuous integration usingtoxandjenkins.Add a pure-Python reference implementation.Move doctests to Sphinx documentation.Bring unit test coverage to 100%.Add ‘setup.py docs’ alias (installsSphinxand dependencies).Add ‘setup.py dev’ alias (runssetup.py developplus installsnoseandcoverage).Drop support for Python 2.4 / 2.5.Remove of ‘zope.testing.doctestunit’ in favor of stdlib’s ‘doctest.Add Python 3 support.3.4.1 (2009-04-05)Update for compatibility with Python 2.6 traceback formats.Use Jython-compatiblebootstrap.py.3.4.0 (2007-07-20)Initial release as a separate project.
Package: zope.httpformdate
This is a small library that extends thezope.httpformlibrary to
support date/time parsing.  It provides a:dateconverter that uses
the parser from thezope.datetimelibrary to convert a variety
of date/time formats to a standarddatetime.datetimeobject.CHANGESVersion 1.0.1 (2009-07-24)Include package data in release.Version 1.0.0 (2009-02-07)First release of zope.httpformdate.  Extracted from zope.app.publisher.
Package: zope.intid
zope.intidThis package provides an API to create integer ids for any object. Later
objects can be looked up by their id as well. This functionality is commonly
used in situations where dealing with objects is undesirable, such as in
search indices or any code that needs an easy hash of an object.Documentation is hosted athttp://zopeintid.readthedocs.ioChanges5.0 (2023-02-21)Add support for Python 3.9, 3.10, 3.11.Drop support for Python 2.7, 3.5, 3.6.Drop support for deprecatedpython setup.py test.4.4.0 (2021-03-19)Fixed deprecation warning forzope.site.hooksin tests.Add support for Python 3.7 and 3.8.Drop support for Python 3.4.Fix incorrect import ofzope.interface.interfaces.IComponentLookupin tests.4.3.0 (2017-07-26)Add support for Python 3.6.Drop support for Python 3.3.4.2.0 (2016-12-08)Raise more informative KeyError subclasses from the utility when intids
or objects cannot be found. This distinguishes them from errors
raised by normal dictionaries or BTrees, and is useful in unit
testing or when persisting intids or sharing them among processes
for later or concurrent use.PropagatePOSKeyErrorfromqueryIdinstead of returning the
default object. This exception indicates a corrupt database, not a
missing object. ThequeryObjectfunction already behaved this way.Stop depending on ZODB for anything except testing.Add support for Python 3.5 and PyPy3 5.2.Drop support for Python 2.6.4.1.0 (2014-12-27)Add support for PyPy (PyPy3 blocked on PyPy3-compatiblezodbpickle).Add support for Python 3.4.4.0.0 (2014-12-20)Add support for testing on Travis.4.0.0a1 (2013-02-22)Add support for Python 3.3.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.Bug fix: ensure that the IntId utility never generates ids greater
than the maxint of the BTree family being used.3.7.2 (2009-12-27)Use the zope.component API in favor of ztapi.Removezope.app.testingdependency.3.7.1 (2009-05-18)Remove dependencies onzope.container.  Instead importObject*Eventclasses fromzope.lifecycleeventand importIContainedfromzope.location.  In order to be able to do
this, depend onzope.lifecycleevent>=3.5.2 andzope.location>=3.5.4.Remove a dependency onzope.container.contained.Contained(this is a dumb base class that defines __parent__ and __name__
as None and declares that the class implements IContained).3.7.0 (2009-02-01)Split out this package fromzope.app.intid. The latter one
now only contains browser views and compatibility imports while
whole IntId functionality is moved here.
Package: zope.introspectorui
zope.introspectoruiWhat is zope.introspectorui?zope.introspectoruiis a set of views for the information objects provided
by zope.introspector.Installing zope.introspectoruizope.introspectoruiis provided as an Python egg on cheeseshop and set
up viazc.buildoutYou may have setuptools already installed for your system Python. In
that case, you may need to upgrade it first because buildout requires
a very recent version:$ sudo easy_install -U setuptoolsIf this command fails because easy_install is not available, there is
a good chance you do not have setuptools available for your system
Python. If so, there is no problem because setuptools will be
installed locally by buildout.Becausezope.introspectoruiis a developer tool, you normally use it
by including the package thesetup.pyfile of your own
package. There will most probably a section calledinstall_requireswhere you add ‘zope.introspector’ like this:...
install_requires=['setuptools',
                  # Add extra requirements here
                  'zope.introspectorui',
                  ...
                  ],Inzc.buildoutbased package setups you can ‘activate’ usage ofzope.introspectoruiafterwards simply by (re)runningbin/buildout.CHANGES0.2 (2009-01-29)Add explicit dependency to zope.location and clean up ZCML activation.0.1 (2008-10-24)Initial Release