Add AdapterRegistry.subscribed() #230
Assignees
Labels
Comments
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Apr 14, 2021
5.3.0 (2020-03-21) ================== - No changes from 5.3.0a1 5.3.0a1 (2021-03-18) ==================== - Improve the repr of ``zope.interface.Provides`` to remove ambiguity about what is being provided. This is especially helpful diagnosing IRO issues. - Allow subclasses of ``BaseAdapterRegistry`` (including ``AdapterRegistry`` and ``VerifyingAdapterRegistry``) to have control over the data structures. This allows persistent implementations such as those based on ZODB to choose more scalable options (e.g., BTrees instead of dicts). See `issue 224 <https://github.com/zopefoundation/zope.interface/issues/224>`_. - Fix a reference counting issue in ``BaseAdapterRegistry`` that could lead to references to interfaces being kept around even when all utilities/adapters/subscribers providing that interface have been removed. This is mostly an issue for persistent implementations. Note that this only corrects the issue moving forward, it does not solve any already corrupted reference counts. See `issue 227 <https://github.com/zopefoundation/zope.interface/issues/227>`_. - Add the method ``BaseAdapterRegistry.rebuild()``. This can be used to fix the reference counting issue mentioned above, as well as to update the data structures when custom data types have changed. - Add the interface method ``IAdapterRegistry.subscribed()`` and implementation ``BaseAdapterRegistry.subscribed()`` for querying directly registered subscribers. See `issue 230 <https://github.com/zopefoundation/zope.interface/issues/230>`_. - Add the maintenance method ``Components.rebuildUtilityRegistryFromLocalCache()``. Most users will not need this, but it can be useful if the ``Components.utilities`` registry is suspected to be out of sync with the ``Components`` object itself (this might happen to persistent ``Components`` implementations in the face of bugs). - Fix the ``Provides`` and ``ClassProvides`` descriptors to stop allowing redundant interfaces (those already implemented by the underlying class or meta class) to produce an inconsistent resolution order. This is similar to the change in ``@implementer`` in 5.1.0, and resolves inconsistent resolution orders with ``zope.proxy`` and ``zope.location``. See `issue 207 <https://github.com/zopefoundation/zope.interface/issues/207>`_.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would be analogous to
AdapterRegistry.registered().My particular use case for this for consistency checking and error correction. When you call
Components.registerUtility(), the utility is supposed to wind up in three places:But we had a situation where a bug (in a subclass) caused only the first and third of those (probably!) to contain the utility. Correcting
_adapterswas easy, because we could check withregistered()whether it was present or not. Correcting_subscribersrequired implementing asubscribed()method.If we can get a
subscribed()method, I could also add the error-detecting/correcting method we wrote toComponents, if desired.The text was updated successfully, but these errors were encountered: