Zope.component

Latest version: v6.0

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

Scan your dependencies

Page 6 of 7

3.7.1

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

- Fix a problem, where ``queryNextUtility`` could fail if the context could
not be adapted to a ``IComponentLookup``.

- 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.

3.7.0

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

- Ensure that ``HookableTests`` are run by the testrunner.

- Add ``zope:view`` and ``zope:resource`` implementations into
``zope.component.zcml`` (dependency loaded with ``zope.component [zcml]``).

3.6.0

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

- 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`` and ``IDefaultViewName`` to ``zope.publisher.interfaces``.

- Move ``IResource`` to ``zope.app.publisher.interfaces``.

- Remove ``IContextDependent``, ``IPresentation``, ``IPresentationRequest``,
``IResourceFactory``, and ``IViewFactory`` completely.

If you used ``IViewFactory`` in context of ``zope.app.form``, there's now
``IWidgetFactory`` in the ``zope.app.form.interfaces`` instead.

- Move ``getNextUtility`` / ``queryNextUtility`` functions here from
``zope.site`` (they were in ``zope.app.component`` even earlier).

- Add a pure-Python ``hookable`` implementation, for use when
``zope.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.

3.5.1

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

- Fix bug introduced in 3.5.0: ``<utility factory="...">`` no longer supported
interfaces declared in Python and always wanted an explicit
``provides="..."`` attribute. https://bugs.launchpad.net/zope3/+bug/251865

3.5.0

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

- 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.

3.4.0

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

No further changes since 3.4.0a1.

Page 6 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.