Saravanan666/pypi-org huggingface dataset:
Package: zope.keyreference
zope.keyreferenceObject references that support stable comparison and hashes.Documentation can be found athttps://zopekeyreference.readthedocs.ioChanges6.0 (2023-04-25)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.11.Make the tests compatible withzope.testing >= 5.5.0.0 (2022-03-25)Remove__cmp__methods. Since the implementation of the rich
comparison methods (__eq__, etc) in 4.0a1, the interpreter won’t
call__cmp__, even on Python 2. Seeissue 10.Add support for Python 3.8, 3.9, and 3.10.Drop support for Python 3.4.4.2.0 (2018-10-26)Add support for Python 3.5, 3.6, and 3.7.Drop support for Python 2.6 and 3.3.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.0a2 (2013-02-25)Ensure that theSimpleKeyReferenceimplementation (used for testing)
also implements rich comparison properly.4.0.0a1 (2013-02-22)Add support for Python 3.3.Replace deprecatedzope.component.adaptsusage with equivalentzope.component.adapterdecorator.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.3.6.4 (2011-11-30)Fix tests broken by removal ofzope.testingfrom test dependencies:
avoid theZODB3module that needs it.3.6.3 (2011-11-29)Prefer the standard libraries doctest module to the one fromzope.testing.3.6.2 (2009-09-15)Make the tests pass with ZODB3.9, which changed the repr() of the persistent
classes.3.6.1 (2009-02-01)Load keyreferences, pickled by old zope.app.keyreference even
if its not installed anymore (so don’t break if one updates a
project that don’t directly depends on zope.app.keyreference).3.6.0 (2009-01-31)Renamezope.app.keyreferencetozope.keyreference.
Package: zope.lifecycleevent
zope.lifecycleeventOverviewIn a loosely-coupled system, events can be used by parts of the system
toinform each otherabout relevant occurrences. Thezope.eventpackage (optionally together withzope.interfaceandzope.component) provides a generic mechanism to dispatch objects
representing those events to interested subscribers (e.g., functions).
This package defines a specific set of event objects and API functions
for describing the life-cycle of objects in the system: object
creation, object modification, and object removal.Documentation is hosted athttps://zopelifecycleevent.readthedocs.ioChanges5.0 (2023-07-06)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.11.4.4 (2022-05-09)Add support for Python 3.8, 3,9, 3.10.Drop support for Python 3.4.4.3 (2018-10-05)Add support for Python 3.7.4.2.0 (2017-07-12)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.Documentation is hosted athttps://zopelifecycleevent.readthedocs.io4.1.0 (2014-12-27)Add support for PyPy3.Add support for Python 3.4.4.0.3 (2013-09-12)Drop the dependency onzope.componentas the interface and
implementation ofObjectEventis now inzope.interface.
Retained the dependency for the tests.Fix:.movedtried to notify the wrong event.4.0.2 (2013-03-08)Add Trove classifiers indicating CPython and PyPy support.4.0.1 (2013-02-11)Addtox.ini.4.0.0 (2013-02-11)Test coverage at 100%.Add support for Python 3.3 and PyPy.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.3.7.0 (2011-03-17)Add convenience functions to parallelzope.lifecycleevent.modifiedfor the other events defined in this package.3.6.2 (2010-09-25)Add not declared, but needed test dependency onzope.component [test].3.6.1 (2010-04-30)Remove dependency on undeclaredzope.testing.doctest.3.6.0 (2009-12-29)Refactor tests to losezope.annotationandzope.dublincoreas
dependencies.3.5.2 (2009-05-17)CopyIObjectMovedEvent,IObjectAddedEvent,IObjectRemovedEventinterfaces andObjectMovedEvent,ObjectAddedEventandObjectRemovedEventclasses here
fromzope.container(plus tests).  The intent is to allow packages
that rely on these interfaces or the event classes to rely onzope.lifecycleevent(which has few dependencies) instead ofzope.container(which has many).3.5.1 (2009-03-09)Remove deprecated code and therefore dependency onzope.deferredimport.Change package’s mailing list address to zope-dev at zope.org, as
zope3-dev at zope.org is now retired.Update package’s description and documentation.3.5.0 (2009-01-31)Remove old module declarations from classes.Usezope.containerinstead ofzope.app.container.3.4.0 (2007-09-01)Initial release as an independent package
Package: zope.login
zope.loginThis package provides login helpers forzope.publisherbased on the concepts ofzope.authentication.
This includes support for HTTP password logins and FTP logins.Documentation is hosted athttps://zopelogin.readthedocs.ioChanges3.0 (2023-08-23)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.11.2.2 (2022-04-29)Add support for Python 3.7, 3.8, 3.9, 3.10.2.1.0 (2017-09-01)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.Host documentation athttps://zopelogin.readthedocs.io/2.0.0 (2014-12-24)Add support for PyPy and PyPy3.Add support for Python 3.4.Add support for testing on Travis.Add support for Python 3.3.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.1.0.0 (2009-12-31)Extracted BasicAuthAdapter and FTPAuth adapters from zope.publisher. They
should have never gone into that package in the first place.
Package: zopemetadatamaker
Table of contentsMain ideazopemetadatamakerHow to useComplete list of optionsWhat to put in the .metadata contentChangelogMain ideaOldZope2products were heavily based onskinsresources. A lot of additional information for those
resources are taken from.metadatafile, so commonly if you have a:my_icon.gif…you will want to have also a:my_icon.gif.metadataIn old Zope/Plone installation (let me say “before Varnish begin to be a Plone standard”) you can use those
metadata for performing associations withHttpCacheobjects, making the user browser to perform some
cache of resources:[default]
title=my_icon.gif
cache=HTTPCachezopemetadatamakerThis product will install for you a new executable:zopemetadatamaker. Using this you can automatically create
your.metadatafiles. when you have a lot of static images, css and javascript files this can save you some times,
for example: you downloaded a big Javascript library with a lot of sub-directories inside and other related resources.How to useThe basic use of the command is something like this:zopemetadatamaker *.gifThis will create for you all “.metadata” related to all gif file found in the current directory. You need to know that:you must provide at least one filter pattersthe directory where files are searched is the current working directory (but you can customize this, see below).Complete list of optionsHere the full documentation:Usage: zopemetadatamaker [options] pattern [patterns]

Bulk creation of .metadata files for Zope skins resources

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -c METADATA, --content=METADATA
                        choose a metadata text different from default; use
                        quoting for multiline input
  -d, --default         print default metadata (if --content is not provided),
                        then exit
  -p PATHS, --path=PATHS
                        directories path where to look for metadata. You can
                        use this multiple times. Default is the current
                        working directory
  --dry-run             dry run, simply print what I would like to do
  -f, --force           force .metadata creation; if another one exists it
                        will be replaced
  -r, --recursive       search and create recursively inside subdirsWhat to put in the .metadata contentThe default metadata content is like this:[default]
title=%(filename)s
cache=HTTPCacheThe%(filename)ssection will be replaced with the original file name. You can use this, or omit it, when
defining you custom.metadata.I use this default content because it is the minimal “cache” information forPlone CMSstatic resouces.Changelog0.1.0 (2011-04-04)Initial release
Package: zope.minmax
zope.minmaxThis package provides support for homogeneous values favoring maximum
or minimum (e.g., numbers) for ZODB conflict resolution.Seehttps://zopeminmax.readthedocs.iofor a detailed description.Changes2.3 (2022-08-30)Drop support for Python 3.4.Add support for Python 3.7, 3.8, 3.9, 3.10.Make theAbstractValueclass public inzope.minmax. It was
already documented to be public.2.2.0 (2017-08-14)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.Bring unit test coverage to 100% (including branches).Convert doctests to Sphinx documentation, including building docs
and running doctest snippets undertox.Host documentation athttps://zopeminmax.readthedocs.io2.1.0 (2014-12-27)Add support for PyPy3.Add support Python 3.4.2.0.0 (2013-02-19)Add support for Python 3.3 and PyPy.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.1.1.2 (2009-09-24)Use the standard Python doctest module instead of the deprecated
zope.testing.doctest.1.1.1 (2009-09-09)Fix homepage link and mailing list address.1.1 (2007-10-02)Refactor package setup.1.0 (2007-09-28)No further changes since 1.0b21.0b2 (2007-07-09)Remove_p_independentmethod fromAbstractValueclass.1.0b1 (2007-07-03)Initial release.
Package: zope.mkzeoinstance
zope.mkzeoinstanceThis package provides a single script,mkzeoinstance, which creates
a standalone ZEO server instance.Changelog5.1.1 (2023-05-05)Makeblob_dirparameter added in 5.1 optional.
(#18)5.1 (2023-04-28)Add configuration option-bresp.--blobsfor passing blob directory
path. (#16)5.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.Drop support for running tests usingpython setup.py test.4.1 (2017-05-26)Fix generatedrunzeoandzeoctlscripts to run with ZEO 5.4.0 (2017-02-28)100% unit test coverage.Drop support for Python 2.6.Add support for Python 3.4, 3.5, and 3.6.Move dependency fromZODB3-> [zdaemon,ZODB,ZEO].
Even though this package doesn’t actually import anything from the last
two, the generated instance won’t be usable unless the host python
has them installed.3.9.6 (2014-12-23)Add support for testing on Travis, and with tox.3.9.5 (2011-10-31)Place the socket used by thezeoctlcontrol process to conmmunicate
with itsrunzeodaemaon in$INSTANCE_HOME/var, instead of$INSTANCE_HOME/etc(which would idealy not be writable by the process).
See:https://bugs.launchpad.net/zope.mkzeoinstance/+bug/1759813.9.4 (2010-04-22)Rename the script / packagemkzeoinstanceto avoid clashing with the
script bundled with ZODB.Add an option to spell the host interface to be listened on, as well as
the port the generated ZEO server configuration.  Thanks to Igor Stroh
for the patch.  See:https://bugs.launchpad.net/zodb/+bug/143361Fix generated templates to cope with the move ofzdaemoncode into
its own project.Fork from the version of themkzeoinstscript contained in
ZODB 3.9.4.
Package: zopen.frs
frs.core is a pure python package for a simple file repository system(FRS).
FRS use a virtual file system which map to the physical disk using a
configuration file. FRS support trash box, metadata and attachments storge,
caching and more.做什么定义了一套虚拟的文件路径系统，可和实际的存储路径映射，避免直接和操作系统的文件系统打交道支持版本管理，可存储文件的历史版本。存放到(.frs目录中)支持缓存／数据转换，比如图片的各种大小的 格式转换和存储，word文件的html预览转换和存储支持垃圾箱，删除的文件可自动存放在垃圾箱里面三级目录映射网站 (zpath) -> FRS  (vpath)FRS (vpath) -> ospath (path)准备文件系统上的文件找到临时文件夹: /tmp/frs>>> import os, tempfile, shutil
>>> temp_dir = tempfile.gettempdir() + '/frs'
>>> if os.path.exists(temp_dir):
...     shutil.rmtree(temp_dir)
>>> os.mkdir(temp_dir)创建缓存文件夹: /tmp/frscache>>> cache = temp_dir + '/frscache'
>>> os.mkdir(cache)创建文件夹结构:/tmp/frs/d1/f11
/tmp/frs/lala/d2/d21
/tmp/frs/lala/d2/f21

   >>> d1 = temp_dir + '/d1'
   >>> os.mkdir(d1)
   >>> f11 = d1 + '/f11'
   >>> open(f11, 'w').write('hello')
   >>> lala = temp_dir + '/lala'
   >>> os.mkdir(lala)
   >>> d2 = lala + '/d2'
   >>> os.mkdir(d2)
   >>> f21 = d2 + '/f21'
   >>> open(f21, 'w').write('hello')
   >>> d21 = d2 + '/d21'
   >>> os.mkdir(d21)初始化得到一个:>>> frs_root = FRS()什么都没有：>>> frs_root.listdir('/')
[]Now we can mount some paths to the top folders:>>> frs_root.mount('d1', d1)
>>> frs_root.mount('d2', d2)同时设置缓存目录>>> frs_root.setCacheRoot(cache)通过配置文件初始化上面很麻烦，通过配置文件更简单配置文件:>>> config = """
... [cache]
... path = /tmp/frscache
...
... [root]
... aa = /tmp/a
... bb = /tmp/b
...
... [site]
... / = /aa
... """加载:>>> from zopen.frs import loadFRSFromConfig
>>> frs_root = loadFRSFromConfig(config)基本的文件系统功能>>> sorted(frs_root.listdir('/'))
['d1', 'd2']
>>> frs_root.isdir('/d1')
True
>>> frs_root.listdir('/d1')
['f11']
>>> frs_root.isdir('/d1/f1')
False
>>> sorted(frs_root.listdir('/d2'))
['d21', 'f21']
>>> frs_root.open('/d2/f21').read()
'hello'现在还不能跨区移动!>>> frs_root.move('/d2/f21', '/d1')
Traceback (most recent call last):
    ...
Exception: ...自动映射其实配置文件中可以在site栏目中配置的。也可以手工配置:>>> frs_root.mapSitepath2Vpath(u'/site1/members', u'/d2')
>>> frs_root.mapSitepath2Vpath(u'/site2/members', u'/d2')
>>> frs_root.mapSitepath2Vpath(u'/', u'/d1')我们看看根据站点路径自动计算的路径:>>> frs_root.sitepath2Vpath('/58080_1/zopen/project/1222/files/uncategoried/aaa.doc')
u'/d1/58080_1/zopen/project/1222/files/uncategoried/aaa.doc'2个站点可以指向同一文件的:>>> frs_root.sitepath2Vpath('/site1/members/aaa.doc')
u'/d2/aaa.doc'
>>> frs_root.sitepath2Vpath('/site2/members/aaa.doc')
u'/d2/aaa.doc'
Package: zope.optionalextension
zope.optionalextensionREADMEThis package provides a distutils extension for building optional C
extensions.  It is intended for use in projects which have a Python reference
implementation of one or more features, and which can function without
needing any C extensions to be successfully compiled.Using the Command with baredistutilsIn thesetup.pyfor your package:from distutils.core import setup

setup(name='your.package',
      ...
      command_packages = ['zope.optionalextension',
                          'distutils.command',
                         ]
      ...
     )You need to ensure thatzope.optionalextensionis installed first
yourself.Using the Command with baresetuptoolsIn thesetup.pyfor your package:from setuptools import setup

setup(name='your.package',
      ...
      setup_requires=['zope.optionalextension'],
      command_packages=['zope.optionalextension',
                        'distutils.command',
                       ]
      ...
     )zope.optionalextensionChangelog1.1 (2010-07-03)Make the package work as a distutilscommand_packagesplugin.1.0 (2010-07-03)Extracted fromzope.i18nmessageid3.5.0.
Package: zope.principalannotation
zope.principalannotationThis package implements annotations for zope.security principals. Common
annotation techniques, likeAttributeAnnotationscannot be applied to
principals, since they are created on the fly for every request.Documentation is hosted athttps://zopeprincipalannotation.readthedocs.io/.Changes5.0 (2023-06-29)Drop support for Python 2.7, 3.5, 3.6.Drop support for deprecatedpython setup.py test.Add support for Python 3.11.4.4 (2022-03-17)Add support for Python 3.8, 3.9 and 3.10.Drop support for Python 3.4.4.3.0 (2018-10-19)Add support for Python 3.7.4.2.0 (2017-08-18)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.4.1.1 (2015-06-02)Replace use of long-deprecatedzope.testing.doctestwith stdlib’sdoctest.4.1.0 (2015-01-09)Accomodate new methods added tozope.annotation.interfaces.IAnnotationsin upcoming zope.annotation 4.4.0 release.4.0.0 (2014-12-24)Add support for PyPy.Add support for Python 3.4.Add support for testing on Travis.4.0.0a2 (2013-02-25)Correct Trove classifiers.4.0.0a1 (2013-02-24)Add support for Python 3.3.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.3.6.1 (2010-05-05)Fix a test failure in nested local site manager setup.Remove dependency on zope.container.3.6.0 (2009-03-09)Initial release. This package was splitted off zope.app.principalannotation
to remove its dependencies on “zope 3 application server” components.In addition, the following changes were made after split off:The IAnnotations implementation was fixed to look in the higher-level
utility not only on__getitem__, but also ongetand__nonzero.Tests was reworked into the README.txt doctest.Added a buildout part that generates Sphinx documentation from the
README.txt
Package: zope.principalregistry
zope.principalregistryThis package provides an authentication utility forzope.authenticationthat uses a simple non-persistent principal registry. This is
typically registered as a global utility, and it is usually configured
in ZCML.Documentation is hosted athttps://zopeprincipalregistry.readthedocs.ioChanges5.0 (2023-07-06)Drop support for Python 2.7, 3.5, 3.6.Drop support for deprecatedpython setup.py test.Add support for Python 3.11.4.3 (2022-07-14)Drop support for Python 3.4.Add support for Python 3.7, 3.8, 3.9, 3.10.4.2.0 (2017-10-01)Fix principal and group objects registered in ZCML or directly with
the principalregistry being invalid under Python 2 (having byte
strings foridinstead of text strings).
Seehttps://github.com/zopefoundation/zope.principalregistry/issues/74.1.0 (2017-09-04)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.Host documentation athttps://zopeprincipalregistry.readthedocs.ioReach 100% test coverage and ensure we remain there.Test PyPy3 on Travis CI.4.0.0 (2014-12-24)Add support for PyPy.  (PyPy3 is pending release of a fix for:https://bitbucket.org/pypy/pypy/issue/1946)Add support for Python 3.4.Add support for testing under Travis.4.0.0a2 (2013-03-03)Make sure that the password is always bytes when passed into the principal
registry.Fix deprecation warnings.4.0.0a1 (2013-02-22)Add support for Python 3.3.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Dropd support for Python 2.4 and 2.5.3.7.1 (2010-09-25)Add test extra to declare test dependency onzope.component [test].Use Python’sdoctestmodule instead of deprecatedzope.testing.doctest.3.7.0 (2009-03-14)Removezope.containerdependency, as contained principals didn’t make any
sense, since PrincipalRegistry never provided IContainer. Also, zope.container
pulls a number dependencies, that are not needed for non-persistent principal
registry (like, ZCML, for example).Set__name__and__parent__by hand to provide some backward-compatibility and
to save a pointer to registry from principal objects.Initial release. This package was split from zope.app.security as a part
of the refactoring process to provide global principal registry without extra
dependencies.
Package: zope.processlifetime
zope.processlifetimeThis package provides interfaces / implementations for events relative
to the lifetime of a server process (startup, database opening, etc.)
These events are usually used withzope.event.Documentation is hosted athttps://zopeprocesslifetime.readthedocs.io/en/latest/Changes3.0 (2023-03-27)Add support for Python 3.11.Drop support for Python 2.7, 3.5, 3.6.Drop support for deprecatedpython setup.py test.2.4 (2022-08-26)Drop support for Python 3.4.Add support for Python 3.8, 3.9, 3.10.2.3.0 (2018-10-05)Add support for Python 3.7.2.2.0 (2017-09-01)Add support for Python 3.5 and 3.6.Drop support for Python 2.6, 3.2 and 3.3.Host documentation athttps://zopeprocesslifetime.readthedocs.io/en/latest/2.1.0 (2014-12-27)Add support for PyPy and PyPy3.Add support for Python 3.4.Add support for testing on Travis.2.0.0 (2013-02-22)Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Add support for Python 3.2 and 3.3Drop support for Python 2.4 and 2.5.1.0 (2009-05-13)Split out event interfaces / implementations fromzope.app.appsetupversion 3.10.2.
Package: zope.psycopgda
psycopgdaThis file outlines the basics of using Zope3 with PostgreSQL via PsycopgDA.Installing PsycopgDACheck out the psycopgda package into a directory in your
PYTHONPATH.  INSTANCE_HOME/lib/python or Zope3/src is usually the
most convenient place:svn co svn://svn.zope.org/repos/main/psycopgda/trunk/psycopgda psycopgdaCopypsycopg-configure.zcmlto thepackage-includesdirectory
of your Zope instance.You can also use the eggified version, by installing it sitewide:easy_install -U psycopgdaIf you’re using buildout, just by listing psycopgda in the ‘eggs’ key
of your buildout.cfg, then buildout should be able to find and fetch it.Creating Database ConnectionsIt is time to add some connections. A connection in Zope 3 is
registered as a utility.Open a web browser on your Zope root folder (http://localhost:8080/if you use the default settings in zope.conf.in).Click on the ‘Manage Site’ action on the right side of the
screen. You should see a screen which reads ‘Common Site Management
Tasks’Around the middle of that page, you should see a link named ‘Add
Utility’. Click on it.Select ‘Psycopg DA’ and type in a name at the bottom of the page.Enter the database connection string.  It looks like this:dbi://username:password@host:port/databasenameClick on the ‘Add’ button.You should be on a page which reads ‘Add Database Connection
Registration’. There you can configure the permission needed to use
the database connection, the name of the registration and the
registration status. You can use any name for ‘Register As’ field,
as long as it doesn’t clash with an existing one. Choose a
permission. Choose between ‘Registered’ and ‘Active’ for the
‘Registration Status’. Only one component of a kind can be ‘Active’
at a time, so be careful.You should be redirected to the ‘Edit’ screen of the connection
utility.If you want to, you can go to the Test page and execute arbitrary
SQL queries to see whether the connection is working as expected.Using SQL ScriptsYou can create SQL Scripts in the content space.  For example:Go to Zope root.Add an SQL script (you can use the Common Tasks box on the left,
or the Add action on the right).Click on the name of your new SQL script.Choose a connection name (the one you entered in step 29) from the
drop-down.Enter your query and click on the ‘Save Changes’ button.You can test the script in the – surprise! – Test page.CHANGES1.1.1 (2008/01/26)Bug: Some classes were incorrectly looked up.1.1.0 (2008/01/26)Feature: Produced a real egg.Restructuring: Moved frompsycopgdatozope.psycopgda.Bug: Fixed issue 561: PsycopgDA ForbiddenAttribute exception.
Package: zope.ptresource
zope.ptresourceNoteThis package is at present not reusable without depending on a large
chunk of the Zope Toolkit and its assumptions. It is maintained by theZope Toolkit project.This package provides a “page template”resource class, a resource
whose content is processed with theZope Page Templatesengine before
being returned to client.The resource factory class is registered for “pt”, “zpt” and “html” file
extensions in the package’sconfigure.zcmlfile.Changes5.0 (2023-03-27)Add support for Python 3.11.Drop support for Python 2.7, 3.5, 3.6.Drop support for deprecatedpython setup.py test.4.3.0 (2021-12-15)Add support for Python 3.8, 3.9 and 3.10.Drop support for Python 3.4.4.2.0 (2018-10-05)Add support for Python 3.7.4.1.0 (2017-08-31)Add support for Python 3.5 and 3.6.Drop support for Python 2.6 and 3.3.4.0.0 (2014-12-24)Add support for PyPy and PyPy3.Add support for Python 3.4.Add support for testing on Travis.4.0.0a1 (2013-02-25)Add support for Python 3.3.Replace deprecatedzope.interface.implementsusage with equivalentzope.interface.implementerdecorator.Drop support for Python 2.4 and 2.5.3.9.0 (2009-08-27)Initial release. This package was split off zope.app.publisher as a part
of refactoring process. It’s now a plugin for another package that was
refactored from zope.app.publisher - zope.browserresource. See its
documentation for more details.Other changes:Don’t render PageTemplateResource when called as the IResource interface
requires that __call__ method should return an absolute URL. When accessed
by browser, it still will be rendered, because “browserDefault” method now
returns a callable that will render the template to browser.