- Drop support for Python 2.7, 3.5, 3.6.
- Fix crash when the environment variable PYTHONOPTIMIZED is set to 2 and docstrings are set to None by the interpreter. (#67)
- Add support for Python 3.10 and 3.11.
- Fix unregistering utilities on old persistent adapter registries.
Previously this could raise
TypeError
. See issue 62.
Remove backwards compatibility imports that were emitting deprecation warnings. This affects certain imports from
zope.component.interfaces
(which should be imported fromzope.interface.interfaces
) as well as certain imports fromzope.component.registery
(import fromzope.interface.registry
), and the entirezope.component.hookable
module. See issue 59.Respect permission value for utility factory registrations (#54)
Add support for Python 3.9
Fix the
<subscriber>
ZCML directive to allow a missingprovides=
attribute when afactory=
is given and the Python object has been decorated with@implementer
and implements a single interface. This has been documented, but hasn't worked before. See issue 9.Make
PersistentAdapterRegistry
use persistent objects (PersistentMapping
andPersistentList
) for its internal data structures instead of plain dicts and lists. This helps make it scalable to larger registry sizes.This requires zope.interface 5.3.0a1 or later.
New registries (and their primary users,
PersistentComponents
and zope.site'sLocalSiteManager
) take full advantage of this automatically. For existing persistent registries to take advantage of this, you must call theirrebuild()
method and commit the transaction.See issue 51.
Fix
zope.interface.interface.provideInterface
and the various search and query methods to use the current site manager instead of always using the global site manager. (provideInterface
is called implicitly when registering components from ZCML.) The search and query methods continue to return interfaces registered in base site managers.See issue 10.
- Improve the documentation, both published and in docstrings. See PR 49.
- Ensure the resolution order of
BaseGlobalComponents
is consistent. See issue 45.
- Add support for Python 3.8.
- Drop support for Python 3.4.
- Fix tests on Python 2 following changes in ZODB 5.5.0.
- Add support for Python 3.7.
- Always install
zope.hookable
as a dependency (thehook
extra is now empty).zope.hookable
respects the PURE_PYTHON environment variable, and has an optional C extension. - Make accessing names that have been moved to
zope.interface
produce aDeprecationWarning
.
- Remove obsolete call of
searchInterface
frominterfaceToName
. See #32
- Add support for Python 3.6.
- Drop support for Python 3.3.
- Drop support for "setup.py test".
- Code coverage reports are now produced and hosted by coveralls.io, and PRs must keep them at 100%.
- Internal test code in
zope.component.testfiles
has been adjusted and in some cases removed.
- When testing
PURE_PYTHON
environments undertox
, avoid poisoning the user's global wheel cache. - Drop support for Python 2.6 and 3.2.
- Add support for Python 3.5.
- Fix test cases for PyPy and PyPy3.
- Add support for Python 3.4.
- Update
boostrap.py
to version 2.2. - Reset the cached
adapter_hooks
atzope.testing.cleanup.cleanUp
time (LP1100501). - Implement ability to specify adapter and utility names in Python. Use
the
@zope.component.named(name)
decorator to specify the name.
- Change "ZODB3" depdendency to "persistent".
tox
now runs all tests for Python 3.2 and 3.3.- Enable buildout for Python 3.
- Fix new failing tests.
- Flesh out PyPI Trove classifiers.
- Add support for Python 3.3.
- Add PyPy and Python 3.2 support:
- Security support omitted until
zope.security
ported. - Persistent registry support omitted until
ZODB
ported (orpersistent
factored out).
- Security support omitted until
- Bring unit test coverage to 100%.
- Remove the long-deprecated
layer
argument to thezope.component.zcml.view
andzope.component.zcml.resource
ZCML directives. - Add support for continuous integration using
tox
andjenkins
. - Got tests to run using
setup.py test
. - Add
Sphinx
documentation. - Add
setup.py docs
alias (installsSphinx
and dependencies). - Add
setup.py dev
alias (runssetup.py develop
plus installsnose
andcoverage
).
- Wrap
with site(foo)
in try/finally (LP768151).
- Add convenience function zope.component.hooks.site (a contextmanager),
so one can write
with site(foo): ...
.
- Move code from
zope.component.registry
which implements a basic nonperistent component registry tozope.interface.registry
. This code was moved fromzope.component
intozope.interface
to make porting systems (such as Pyramid) that rely only on a basic component registry to Python 3 possible without needing to port the entirety of thezope.component
package. Backwards compatibility import shims have been left behind inzope.component
, so this change will not break any existing code. - Move interfaces from
zope.component.interfaces
tozope.interface.interfaces
:ComponentLookupError
,Invalid
,IObjectEvent
,ObjectEvent
,IComponentLookup
,IRegistration
,IUtilityRegistration
,IAdapterRegistration
,ISubscriptionAdapterRegistration
,IHandlerRegistration
,IRegistrationEvent
,RegistrationEvent
,IRegistered
,Registered
,IUnregistered
,Unregistered
,IComponentRegistry
, andIComponents
. Backwards compatibility shims left in place. - Depend on
zope.interface
>= 3.8.0.
- Remove the
docs
extra and thesphinxdoc
recipe. - Create a
security
extra to move security-related dependencies out of thetest
extra. - Use the new
zope.testrunner
package for tests. - Add a basic test for the
configure.zcml
file provided.
- Fix test requirements specification.
- Prefer the standard library
doctest
to the one fromzope.testing
.
- The ZCML directives provided by
zope.component
now register the components in the registry returned bygetSiteManager
instead of the global registry. This change allows the hooking of thegetSiteManager
method before the load of a ZCML file to register the components in a custom registry.
- Fix a bug introduced by recent refactoring, where passing
CheckerPublic
tosecurityAdapterFactory
wrongly wrapped the factory into aLocatingUntrustedAdapterFactory
.
- Modify the tests to avoid allowing the tested testrunner to be influenced
by options of the outer testrunner, such a the
-v
option.
- Add testlayer support. It is now possible to load a ZCML file within
tests more easily. See
src/zope/component/testlayer.py
andsrc/zope/component/testlayer.txt
.
- Remove the dependencies on
zope.proxy
andzope.security
from the zcml extra:zope.component
no longer has a hard dependency on them; the support for security proxied components ZCML registrations is enabled only ifzope.security
andzope.proxy
are available. - Move the
IPossibleSite
andISite
interfaces here fromzope.location
as they are dealing withzope.component
's concept of a site, but not with location. - Move the
zope.site.hooks
functionality tozope.component.hooks
as it isn't actually dealing withzope.site
's concept of a site.
Fix a problem, where
queryNextUtility
could fail if the context could not be adapted to aIComponentLookup
.Fix 2 related bugs:
When a utility is registered and there was previously a utility registered for the same interface and name, then the old utility is unregistered. The 2 bugs related to this:
- There was no
Unregistered
for the implicit unregistration. Now there is. - The old utility was still held and returned by
getAllUtilitiesRegisteredFor
. In other words, it was still considered registered, eeven though it wasn't. A particularly negative consequence of this is that the utility is held in memory or in the database even though it isn't used.
- There was no
- Ensure that
HookableTests
are run by the testrunner. - Add
zope:view
andzope:resource
implementations intozope.component.zcml
(dependency loaded withzope.component [zcml]
).
IMPORTANT: the interfaces that were defined in the
zope.component.bbb.interfaces
and deprecated for years are now (re)moved. However, some packages, including part of zope framework were still using those interfaces. They will be adapted for this change. If you were using some of those interfaces, you need to adapt your code as well:Move
IView
andIDefaultViewName
tozope.publisher.interfaces
.Move
IResource
tozope.app.publisher.interfaces
.Remove
IContextDependent
,IPresentation
,IPresentationRequest
,IResourceFactory
, andIViewFactory
completely.If you used
IViewFactory
in context ofzope.app.form
, there's nowIWidgetFactory
in thezope.app.form.interfaces
instead.
Move
getNextUtility
/queryNextUtility
functions here fromzope.site
(they were inzope.app.component
even earlier).Add a pure-Python
hookable
implementation, for use whenzope.hookable
is not present.Remove use of
zope.deferredimport
by breaking import cycles.Cleanup package documentation and changelog a bit. Add sphinx-based documentation building command to the buildout.
Remove deprecated code.
Change package's mailing list address to zope-dev at zope.org, because zope3-dev at zope.org is now retired.
- Fix bug introduced in 3.5.0:
<utility factory="...">
no longer supported interfaces declared in Python and always wanted an explicitprovides="..."
attribute. https://bugs.launchpad.net/zope3/+bug/251865
- Support registration of utilities via factories through the component registry and return factory information in the registration information. Fixes https://bugs.launchpad.net/zope3/+bug/240631
- Optimize
un/registerUtility
by storing an optimized data structure for efficient retrieval of already registered utilities. This avoids looping over all utilities when registering a new one.
No further changes since 3.4.0a1.
Corresponds to zope.component
from Zope 3.4.0a1.
- In the Zope 3.3.x series,
zope.component
was simplified yet once more. See http://wiki.zope.org/zope3/LocalComponentManagementSimplification for the proposal describing the changes.
- Fix packaging bug:
package_dir
must be a relative path.
- Packaging change: suppress inclusion of
setup.cfg
insdist
builds.
Corresponds to the verison of the zope.component
package shipped as part
of the Zope 3.2.0 release.
- Deprecated services and related APIs. The adapter and utility registries are now available directly via the site manager's 'adapters' and 'utilities' attributes, respectively. Services are accessible, but deprecated, and will be removed in Zope 3.3.
- Deprecated all presentation-related APIs, including all view-related API functions. Use the adapter API functions instead. See http://dev.zope.org/Zope3/ImplementViewsAsAdapters`
- Deprecated
contextdependent
package: site managers are now looked up via a thread global, set during URL traversal. Thecontext
argument is now always optional, and should no longer be passed.
Corresponds to the verison of the zope.component
package shipped as part of
the Zope X3.0.0 release.