From ea2e7f0631c505c8b605c92db16686bb0e16921d Mon Sep 17 00:00:00 2001 From: adam Date: Wed, 14 Apr 2021 04:55:44 +0000 Subject: [PATCH] py-ZopeInterface: updated to 5.3.0 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 `_. --- devel/py-ZopeInterface/Makefile | 4 ++-- devel/py-ZopeInterface/distinfo | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/devel/py-ZopeInterface/Makefile b/devel/py-ZopeInterface/Makefile index 9d0095d5debd..f555f0ebd2b1 100644 --- a/devel/py-ZopeInterface/Makefile +++ b/devel/py-ZopeInterface/Makefile @@ -1,6 +1,6 @@ -# $NetBSD: Makefile,v 1.35 2021/01/03 21:43:21 adam Exp $ +# $NetBSD: Makefile,v 1.36 2021/04/14 04:55:44 adam Exp $ -DISTNAME= zope.interface-5.2.0 +DISTNAME= zope.interface-5.3.0 PKGNAME= ${PYPKGPREFIX}-${DISTNAME:S/zope.i/ZopeI/} CATEGORIES= devel python MASTER_SITES= ${MASTER_SITE_PYPI:=z/zope.interface/} diff --git a/devel/py-ZopeInterface/distinfo b/devel/py-ZopeInterface/distinfo index 3708c3d67578..55ba9bfbf28e 100644 --- a/devel/py-ZopeInterface/distinfo +++ b/devel/py-ZopeInterface/distinfo @@ -1,6 +1,6 @@ -$NetBSD: distinfo,v 1.24 2021/01/03 21:43:21 adam Exp $ +$NetBSD: distinfo,v 1.25 2021/04/14 04:55:44 adam Exp $ -SHA1 (zope.interface-5.2.0.tar.gz) = 7e0e62fa44bdae42266b4fdb7121857e14ef5f11 -RMD160 (zope.interface-5.2.0.tar.gz) = 5d2668d792db66c605831ab2b36060485fdad49c -SHA512 (zope.interface-5.2.0.tar.gz) = 64688b8a823d63fc78720ee15d59cc54c07a700dc45e46336cb23cd1a0a3eb998284a4d954d3fa08c7f26b35583c0284fb2fcd18f84f3133ce93f7c3ade0a988 -Size (zope.interface-5.2.0.tar.gz) = 227058 bytes +SHA1 (zope.interface-5.3.0.tar.gz) = f1ceb28f8edc526b5bc5a335e357af1d9ed44a08 +RMD160 (zope.interface-5.3.0.tar.gz) = 9a8ada33bdfec240e2665cd1c07cc9b104d2bd25 +SHA512 (zope.interface-5.3.0.tar.gz) = 3544c64d64f32e4635031325b38500b8ed5888b03821c5ff2e07c2d88bb50ccb0b6fe24c6a55813bbe05caf2b847be832182e04dcd8e9ff29f1e68c1fda7c680 +Size (zope.interface-5.3.0.tar.gz) = 241964 bytes