Bump zope-interface from 4.4.3 to 5.4.0

[dependabot-preview]

Bumps zope-interface from 4.4.3 to 5.4.0.

Changelog

Sourced from zope-interface's changelog.

5.4.0 (2021-04-15)

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

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

5.2.0 (2020-11-05)

• Add documentation section Persistency and Equality (#218).
• Create arm64 wheels.
• Add support for Python 3.9.

5.1.2 (2020-10-01)

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

5.1.1 (2020-09-30)

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

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

  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.

... (truncated)

Commits

• 324ba68 Preparing release 5.4.0
• 24b6a01 Merge pull request #240 from zopefoundation/issue239
• 6a293da Finish sentence in docstring. [skip ci]
• 253456f Merge pull request #238 from zopefoundation/issue193
• 8a0a8f1 Make C's providedBy stop ignoring all errors and catch only AttributeError.
• eb542a8 Make Declaration.add try harder to produce consistent resolution orders.
• 4a686fc Merge pull request #237 from zopefoundation/issue236
• ce8f66f Update repr() and str() of some common objects.
• e6d3805 - prepare release 5.3.0
• ef0b7da - ignore virtualenv artifacts
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)