chore(deps): update dependency zope.interface to v5.5.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
zope.interface	==5.0.1 -> ==5.5.2

---

Release Notes

zopefoundation/zope.interface (zope.interface)

v5.5.2

Compare Source

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

• Add support for building arm64 wheels on macOS.

v5.5.1

Compare Source

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

• Add support for final Python 3.11 release.

v5.5.0

Compare Source

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

• Add support for Python 3.10 and 3.11 (as of 3.11.0rc2).

• Add missing Trove classifier showing support for Python 3.9.

• Add some more entries to zope.interface.interfaces.__all__.

• Disable unsafe math optimizations in C code. See pull request 262 <https://github.com/zopefoundation/zope.interface/pull/262>_.

v5.4.0

Compare Source

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

• Make the C implementation of the __providedBy__ descriptor stop
  ignoring all errors raised when accessing the instance's
  __provides__. Now it behaves like the Python version and only
  catches AttributeError. The previous behaviour could lead to
  crashing the interpreter in cases of recursion and errors. See
  issue 239 <https://github.com/zopefoundation/zope.interface/issues>_.

• Update the repr() and str() of various objects to be shorter
  and more informative. In many cases, the repr() is now something
  that can be evaluated to produce an equal object. For example, what
  was previously printed as <implementedBy builtins.list> is now
  shown as classImplements(list, IMutableSequence, IIterable). See
  issue 236 <https://github.com/zopefoundation/zope.interface/issues/236>_.

• Make Declaration.__add__ (as in implementedBy(Cls) + ISomething) try harder to preserve a consistent resolution order
  when the two arguments share overlapping pieces of the interface
  inheritance hierarchy. Previously, the right hand side was always
  put at the end of the resolution order, which could easily produce
  invalid orders. See issue 193 <https://github.com/zopefoundation/zope.interface/issues/193>_.

v5.3.0

Compare Source

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

• No changes from 5.3.0a1

v5.2.0

Compare Source

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

• Add documentation section Persistency and Equality
  (#&#8203;218 <https://github.com/zopefoundation/zope.interface/issues/218>_).

• Create arm64 wheels.

• Add support for Python 3.9.

v5.1.2

Compare Source

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

• Make sure to call each invariant only once when validating invariants.
  Previously, invariants could be called multiple times because when an
  invariant is defined in an interface, it's found by in all interfaces
  inheriting from that interface. See pull request 215 <https://github.com/zopefoundation/zope.interface/pull/215/>_.

v5.1.1

Compare Source

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

• Fix the method definitions of IAdapterRegistry.subscribe,
  subscriptions and subscribers. Previously, they all were
  defined to accept a name keyword argument, but subscribers have
  no names and the implementation of that interface did not accept
  that argument. See issue 208 <https://github.com/zopefoundation/zope.interface/issues/208>_.

• Fix a potential reference leak in the C optimizations. Previously,
  applications that dynamically created unique Specification
  objects (e.g., used @implementer on dynamic classes) could
  notice a growth of small objects over time leading to increased
  garbage collection times. See issue 216 <https://github.com/zopefoundation/zope.interface/issues/216>_.

  .. caution::

  This leak could prevent interfaces used as the bases of
  other interfaces from being garbage collected. Those interfaces
  will now be collected.

  One way in which this would manifest was that weakref.ref
  objects (and things built upon them, like
  Weak[Key|Value]Dictionary) would continue to have access to
  the original object even if there were no other visible
  references to Python and the original object should have been
  collected. This could be especially problematic for the
  WeakKeyDictionary when combined with dynamic or local
  (created in the scope of a function) interfaces, since interfaces
  are hashed based just on their name and module name. See the
  linked issue for an example of a resulting KeyError.

  Note that such potential errors are not new, they are just once
  again a possibility.

v5.1.0

Compare Source

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

• Make @implementer(*iface) and classImplements(cls, *iface)
  ignore redundant interfaces. If the class already implements an
  interface through inheritance, it is no longer redeclared
  specifically for cls. This solves many instances of inconsistent
  resolution orders, while still allowing the interface to be declared
  for readability and maintenance purposes. See issue 199 <https://github.com/zopefoundation/zope.interface/issues/199>_.

• Remove all bare except: statements. Previously, when accessing
  special attributes such as __provides__, __providedBy__,
  __class__ and __conform__, this package wrapped such access
  in a bare except: statement, meaning that many errors could pass
  silently; typically this would result in a fallback path being taken
  and sometimes (like with providedBy()) the result would be
  non-sensical. This is especially true when those attributes are
  implemented with descriptors. Now, only AttributeError is
  caught. This makes errors more obvious.

  Obviously, this means that some exceptions will be propagated
  differently than before. In particular, RuntimeError raised by
  Acquisition in the case of circular containment will now be
  propagated. Previously, when adapting such a broken object, a
  TypeError would be the common result, but now it will be a more
  informative RuntimeError.

  In addition, ZODB errors like POSKeyError could now be
  propagated where previously they would ignored by this package.

  See issue 200 <https://github.com/zopefoundation/zope.interface/issues/200>_.

• Require that the second argument (bases) to InterfaceClass is
  a tuple. This only matters when directly using InterfaceClass to
  create new interfaces dynamically. Previously, an individual
  interface was allowed, but did not work correctly. Now it is
  consistent with type and requires a tuple.

• Let interfaces define custom __adapt__ methods. This implements
  the other side of the :pep:246 adaptation protocol: objects being
  adapted could already implement __conform__ if they know about
  the interface, and now interfaces can implement __adapt__ if
  they know about particular objects. There is no performance penalty
  for interfaces that do not supply custom __adapt__ methods.

  This includes the ability to add new methods, or override existing
  interface methods using the new @interfacemethod decorator.

  See issue 3 <https://github.com/zopefoundation/zope.interface/issues/3>_.

• Make the internal singleton object returned by APIs like
  implementedBy and directlyProvidedBy for objects that
  implement or provide no interfaces more immutable. Previously an
  internal cache could be mutated. See issue 204 <https://github.com/zopefoundation/zope.interface/issues/204>_.

v5.0.2

Compare Source

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

• Ensure that objects that implement no interfaces (such as direct
  subclasses of object) still include Interface itself in
  their __iro___ and __sro___. This fixes adapter registry
  lookups for such objects when the adapter is registered for
  Interface. See issue 197 <https://github.com/zopefoundation/zope.interface/issues/197>_.

---

Configuration

📅 Schedule: Branch creation - "every 2 weeks on Monday before 7am" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.