Zope.component

Latest version: v6.0

Safety actively analyzes 688896 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 7

3.9.4

==================

- Prefer the standard library ``doctest`` to the one from ``zope.testing``.

3.9.3

==================

- The ZCML directives provided by ``zope.component`` now register the
components in the registry returned by ``getSiteManager`` instead of the
global registry. This change allows the hooking of the ``getSiteManager``
method before the load of a ZCML file to register the components in a
custom registry.

3.9.2

==================

- Fix a bug introduced by recent refactoring, where passing
``CheckerPublic`` to ``securityAdapterFactory`` wrongly wrapped the factory
into a ``LocatingUntrustedAdapterFactory``.

3.9.1

==================

- Modify the tests to avoid allowing the tested testrunner to be influenced
by options of the outer testrunner, such a the ``-v`` option.

3.9.0

==================

- Add testlayer support. It is now possible to load a ZCML file within
tests more easily. See ``src/zope/component/testlayer.py`` and
``src/zope/component/testlayer.txt``.

3.8.0

==================

- Remove the dependencies on ``zope.proxy`` and ``zope.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 if ``zope.security`` and ``zope.proxy`` are available.

- Move the ``IPossibleSite`` and ``ISite`` interfaces here from
``zope.location`` as they are dealing with ``zope.component``'s concept of
a site, but not with location.

- Move the ``zope.site.hooks`` functionality to ``zope.component.hooks`` as it
isn't actually dealing with ``zope.site``'s concept of a site.

Page 5 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.