==================
- Remove backwards compatibility imports that were emitting
deprecation warnings. This affects certain imports from
``zope.component.interfaces`` (which should be imported from
``zope.interface.interfaces``) as well as certain imports from
``zope.component.registery`` (import from
``zope.interface.registry``), and the entire
``zope.component.hookable`` module. See `issue 59
<https://github.com/zopefoundation/zope.component/issues/59>`_.
- Respect permission value for utility factory registrations
(`54 <https://github.com/zopefoundation/zope.component/issues/54>`_)
- Add support for Python 3.9
- Fix the ``<subscriber>`` ZCML directive to allow a missing
``provides=`` attribute when a ``factory=`` 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
<https://github.com/zopefoundation/zope.component/issues/9>`_.
- Make ``PersistentAdapterRegistry`` use persistent objects
(``PersistentMapping`` and ``PersistentList``) 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's ``LocalSiteManager``) take full advantage of this
automatically. For existing persistent registries to take advantage
of this, you must call their ``rebuild()`` method and commit the
transaction.
See `issue 51 <https://github.com/zopefoundation/zope.component/issues/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 <https://github.com/zopefoundation/zope.component/issues/51>`_.