开源软件构建与测试

_service:tar_scm:python-zope-interface.spec Changed

@@ -1,11 +1,11 @@
 %global _empty_manifest_terminate_build 0
 Name:           python-zope-interface
-Version:        5.4.0
-Release:        2
+Version:        5.5.2
+Release:        1
 Summary:        Interfaces for Python
 License:        ZPL 2.1
 URL:            https://github.com/zopefoundation/zope.interface
-Source0:        https://files.pythonhosted.org/packages/ae/58/e0877f58daa69126a5fb325d6df92b20b77431cd281e189c5ec42b722f58/zope.interface-5.4.0.tar.gz
+Source0:        https://files.pythonhosted.org/packages/38/6f/fbfb7dde38be7e5644bb342c4c7cdc444cd5e2ffbd70d091263b3858a8cb/zope.interface-5.5.2.tar.gz
 %description
 This package is intended to be independently reusable in any Python project.
 It is maintained by the Zope Toolkit project.
@@ -88,6 +88,12 @@
 %{_docdir}/*
 
 %changelog
+* Thu Dec 15 2022 chendexi <chendexi@kylinos.cn> - 5.5.2-1
+- Upgrade package to version 5.5.2
+
+* Wed Nov 09 2022 jiangxinyu <jiangxinyu@kylinos.cn> - 5.5.1-1
+- Upgrade package to version 5.5.1
+
 * Thu Mar 03 2022 zhaoshuang <zhaoshuang@uniontech.com> - 5.4.0-2
 - remove some unnecessary buildrequires

_service Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/_static Deleted

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/_static/.gitignore Deleted

_service:tar_scm:zope.interface-5.4.0.tar.gz/.coveragerc -> _service:tar_scm:zope.interface-5.5.2.tar.gz/.coveragerc Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/.manylinux-install.sh -> _service:tar_scm:zope.interface-5.5.2.tar.gz/.manylinux-install.sh Changed

@@ -1,4 +1,6 @@
 #!/usr/bin/env bash
+# Generated from:
+# https://github.com/zopefoundation/meta/tree/master/config/c-code
 
 set -e -x
 
@@ -21,21 +23,42 @@
 ls -ld /cache
 ls -ld /cache/pip
 
+# We need some libraries because we build wheels from scratch:
+yum -y install libffi-devel
+
+tox_env_map() {
+    case $1 in
+        *"cp27"*) echo 'py27';;
+        *"cp35"*) echo 'py35';;
+        *"cp36"*) echo 'py36';;
+        *"cp37"*) echo 'py37';;
+        *"cp38"*) echo 'py38';;
+        *"cp39"*) echo 'py39';;
+        *"cp310"*) echo 'py310';;
+        *"cp311"*) echo 'py311';;
+        *) echo 'py';;
+    esac
+}
+
 # Compile wheels
 for PYBIN in /opt/python/*/bin; do
-    if  "${PYBIN}" == *"cp27"*  || \
+    if \
+        "${PYBIN}" == *"cp27"*  || \
         "${PYBIN}" == *"cp35"*  || \
+        "${PYBIN}" == *"cp311"*  || \
         "${PYBIN}" == *"cp36"*  || \
         "${PYBIN}" == *"cp37"*  || \
         "${PYBIN}" == *"cp38"*  || \
-        "${PYBIN}" == *"cp39"* ; then
+        "${PYBIN}" == *"cp39"*  || \
+        "${PYBIN}" == *"cp310"*  ; then
         "${PYBIN}/pip" install -e /io/
         "${PYBIN}/pip" wheel /io/ -w wheelhouse/
         if  `uname -m` == 'aarch64' ; then
-         cd /io/
-         "${PYBIN}/pip" install tox
-         "${PYBIN}/tox" -e py
-         cd ..
+          cd /io/
+          ${PYBIN}/pip install tox
+          TOXENV=$(tox_env_map "${PYBIN}")
+          ${PYBIN}/tox -e ${TOXENV}
+          cd ..
         fi
         rm -rf /io/build /io/*.egg-info
     fi

_service:tar_scm:zope.interface-5.4.0.tar.gz/.manylinux.sh -> _service:tar_scm:zope.interface-5.5.2.tar.gz/.manylinux.sh Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/CHANGES.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/CHANGES.rst Changed

@@ -2,6 +2,31 @@
  Changes
 =========
 
+5.5.2 (2022-11-17)
+==================
+
+- Add support for building arm64 wheels on macOS.
+
+
+5.5.1 (2022-11-03)
+==================
+
+- Add support for final Python 3.11 release.
+
+
+5.5.0 (2022-10-10)
+==================
+
+- 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>`_.
+
+
 5.4.0 (2021-04-15)
 ==================
 
@@ -960,14 +985,14 @@
 3.2.0 (2006-01-05)
 ==================
 
-- Corresponds to the verison of the zope.interface package shipped as part of
+- Corresponds to the version of the zope.interface package shipped as part of
   the Zope 3.2.0 release.
 
 
 3.1.0 (2005-10-03)
 ==================
 
-- Corresponds to the verison of the zope.interface package shipped as part of
+- Corresponds to the version of the zope.interface package shipped as part of
   the Zope 3.1.0 release.
 
 - Made attribute resolution order consistent with component lookup order,
@@ -980,7 +1005,7 @@
 3.0.1 (2005-07-27)
 ==================
 
-- Corresponds to the verison of the zope.interface package shipped as part of
+- Corresponds to the version of the zope.interface package shipped as part of
   the Zope X3.0.1 release.
 
 - Fix a bug reported by James Knight, which caused adapter registries
@@ -990,5 +1015,5 @@
 3.0.0 (2004-11-07)
 ==================
 
-- Corresponds to the verison of the zope.interface package shipped as part of
+- Corresponds to the version of the zope.interface package shipped as part of
   the Zope X3.0.0 release.

_service:tar_scm:zope.interface-5.5.2.tar.gz/CONTRIBUTING.md Added

_service:tar_scm:zope.interface-5.4.0.tar.gz/MANIFEST.in -> _service:tar_scm:zope.interface-5.5.2.tar.gz/MANIFEST.in Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/PKG-INFO -> _service:tar_scm:zope.interface-5.5.2.tar.gz/PKG-INFO Changed

@@ -1,1040 +1,12 @@
 Metadata-Version: 2.1
 Name: zope.interface
-Version: 5.4.0
+Version: 5.5.2
 Summary: Interfaces for Python
 Home-page: https://github.com/zopefoundation/zope.interface
 Author: Zope Foundation and Contributors
 Author-email: zope-dev@zope.org
 License: ZPL 2.1
-Description: ====================
-         ``zope.interface``
-        ====================
-        
-        .. image:: https://img.shields.io/pypi/v/zope.interface.svg
-            :target: https://pypi.python.org/pypi/zope.interface/
-            :alt: Latest Version
-        
-        .. image:: https://img.shields.io/pypi/pyversions/zope.interface.svg
-                :target: https://pypi.org/project/zope.interface/
-                :alt: Supported Python versions
-        
-        .. image:: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml/badge.svg
-                :target: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml
-        
-        .. image:: https://readthedocs.org/projects/zopeinterface/badge/?version=latest
-                :target: https://zopeinterface.readthedocs.io/en/latest/
-                :alt: Documentation Status
-        
-        This package is intended to be independently reusable in any Python
-        project. It is maintained by the `Zope Toolkit project
-        <https://zopetoolkit.readthedocs.io/>`_.
-        
-        This package provides an implementation of "object interfaces" for Python.
-        Interfaces are a mechanism for labeling objects as conforming to a given
-        API or contract. So, this package can be considered as implementation of
-        the `Design By Contract`_ methodology support in Python.
-        
-        .. _Design By Contract: http://en.wikipedia.org/wiki/Design_by_contract
-        
-        For detailed documentation, please see https://zopeinterface.readthedocs.io/en/latest/
-        
-        =========
-         Changes
-        =========
-        
-        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 <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>`_.
-        
-        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>`_.
-        
-        5.2.0 (2020-11-05)
-        ==================
-        
-        - Add documentation section ``Persistency and Equality``
-          (`#218 <https://github.com/zopefoundation/zope.interface/issues/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
-          <https://github.com/zopefoundation/zope.interface/pull/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
-          <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
-             ``WeakKey|ValueDictionary``) 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.
-        
-        5.1.0 (2020-04-08)
-        ==================
-        
-        - 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.

_service:tar_scm:zope.interface-5.5.2.tar.gz/appveyor.yml Added

@@ -0,0 +1,52 @@
+# Generated from:
+# https://github.com/zopefoundation/meta/tree/master/config/c-code
+environment:
+  # Currently the builds use @mgedmin's Appveyor account.  The PyPI token
+  # belongs to zope.wheelbuilder, which is managed by @mgedmin and @dataflake.
+  
+  global:
+    TWINE_USERNAME: __token__
+    TWINE_PASSWORD:
+      secure: aoZC/+rvJKg8B5GMGIxd1X2q2bz7SMl8G3810BID9U8PXFqM0FbWaK9fZ9qcU0UyG2xJsK56Fb6+L6g27I0Lg8UFNhlU1zLAuMSgJQbHsqawFgSY067IdJB68pp34d/oEyxMrJvAKENHH77Fe4KGDssLlk5WnnYS3DA9b66p5imP+1DTtkq5/gMtoG4nZTBtVos7J2kkYTQ5t4BjzTQxPMC3bStNnvuuB0orX4AoCyTrOR1wdZFiNKLzbVnrJCNn24t/n3kG9WrxbnKlrbOm4A==
+
+  matrix:
+    - python: 27-x64
+    - python: 35-x64
+    - python: 36-x64
+    - python: 37-x64
+    - python: 38-x64
+    - python: 39-x64
+    - python: 310-x64
+    - python: 311-x64
+
+install:
+  - "SET PYTHONVERSION=%PYTHON%"
+  - "SET PATH=C:\\Python%PYTHON%;c:\\Python%PYTHON%\\scripts;%PATH%"
+  - ps: |
+      $env:PYTHON = "C:\\Python${env:PYTHON}"
+      if (-not (Test-Path $env:PYTHON)) {
+        curl -o install_python.ps1 https://raw.githubusercontent.com/matthew-brett/multibuild/11a389d78892cf90addac8f69433d5e22bfa422a/install_python.ps1
+        .\install_python.ps1
+      }
+  - ps: if (-not (Test-Path $env:PYTHON)) { throw "No $env:PYTHON" }
+  - echo "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64 > "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat"
+  - python -m pip install -U pip
+  - pip install -U setuptools wheel
+  - pip install -U -e .test
+
+matrix:
+  fast_finish: true
+
+build_script:
+  - python -W ignore setup.py -q bdist_wheel
+
+test_script:
+  - python -m unittest discover -s src
+artifacts:
+  - path: 'dist\*.whl'
+    name: wheel
+
+deploy_script:
+  - ps: if ($env:APPVEYOR_REPO_TAG -eq $TRUE) { pip install twine; twine upload --skip-existing dist\*.whl }
+
+deploy: on

_service:tar_scm:zope.interface-5.5.2.tar.gz/benchmarks Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/benchmarks/micro.py Added

@@ -0,0 +1,348 @@
+import pyperf
+
+from zope.interface import Interface
+from zope.interface import classImplements
+from zope.interface import implementedBy
+from zope.interface.interface import InterfaceClass
+from zope.interface.registry import Components
+
+# Long, mostly similar names are a worst case for equality
+# comparisons.
+ifaces = 
+    InterfaceClass('I' + ('0' * 20) + str(i), (Interface,), {})
+    for i in range(100)
+
+
+class IWideInheritance(*ifaces):
+    """
+    Inherits from 100 unrelated interfaces.
+    """
+
+class WideInheritance(object):
+    pass
+classImplements(WideInheritance, IWideInheritance)
+
+def make_deep_inheritance():
+    children = 
+    base = Interface
+    for iface in ifaces:
+        child = InterfaceClass('IDerived' + base.__name__, (iface, base,), {})
+        base = child
+        children.append(child)
+    return children
+
+deep_ifaces = make_deep_inheritance()
+
+class DeepestInheritance(object):
+    pass
+classImplements(DeepestInheritance, deep_ifaces-1)
+
+
+class ImplementsNothing(object):
+    pass
+
+
+class HasConformReturnNone(object):
+    def __conform__(self, iface):
+        return None
+
+
+class HasConformReturnObject(object):
+    def __conform__(self, iface):
+        return self
+
+
+def make_implementer(iface):
+    c = type('Implementer' + iface.__name__, (object,), {})
+    classImplements(c, iface)
+    return c
+
+implementers = 
+    make_implementer(iface)
+    for iface in ifaces
+
+
+providers = 
+    implementer()
+    for implementer in implementers
+
+
+INNER = 100
+
+def bench_in(loops, o):
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            o.__contains__(Interface)
+
+    return pyperf.perf_counter() - t0
+
+def bench_sort(loops, objs):
+    import random
+    rand = random.Random(8675309)
+
+    shuffled = list(objs)
+    rand.shuffle(shuffled)
+
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            sorted(shuffled)
+
+    return pyperf.perf_counter() - t0
+
+def bench_query_adapter(loops, components, objs=providers):
+    components_queryAdapter = components.queryAdapter
+    # One time through to prime the caches
+    for iface in ifaces:
+        for provider in providers:
+            components_queryAdapter(provider, iface)
+
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for iface in ifaces:
+            for provider in objs:
+                components_queryAdapter(provider, iface)
+    return pyperf.perf_counter() - t0
+
+
+def bench_getattr(loops, name, get=getattr):
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            get(Interface, name) # 1
+            get(Interface, name) # 2
+            get(Interface, name) # 3
+            get(Interface, name) # 4
+            get(Interface, name) # 5
+            get(Interface, name) # 6
+            get(Interface, name) # 7
+            get(Interface, name) # 8
+            get(Interface, name) # 9
+            get(Interface, name) # 10
+    return pyperf.perf_counter() - t0
+
+
+def bench_iface_call_no_conform_no_alternate_not_provided(loops):
+    inst = ImplementsNothing()
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            for iface in ifaces:
+                try:
+                    iface(inst)
+                except TypeError:
+                    pass
+                else:
+                    raise TypeError("Should have failed")
+    return pyperf.perf_counter() - t0
+
+
+def bench_iface_call_no_conform_w_alternate_not_provided(loops):
+    inst = ImplementsNothing()
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            for iface in ifaces:
+                iface(inst, 42)
+    return pyperf.perf_counter() - t0
+
+
+def bench_iface_call_w_conform_return_none_not_provided(loops):
+    inst = HasConformReturnNone()
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            for iface in ifaces:
+                iface(inst, 42)
+    return pyperf.perf_counter() - t0
+
+
+def bench_iface_call_w_conform_return_non_none_not_provided(loops):
+    inst = HasConformReturnObject()
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            for iface in ifaces:
+                iface(inst)
+    return pyperf.perf_counter() - t0
+
+def _bench_iface_call_simple(loops, inst):
+    t0 = pyperf.perf_counter()
+    for _ in range(loops):
+        for _ in range(INNER):
+            for iface in ifaces:
+                iface(inst)
+    return pyperf.perf_counter() - t0
+
+
+def bench_iface_call_no_conform_provided_wide(loops):
+    return _bench_iface_call_simple(loops, WideInheritance())
+
+
+def bench_iface_call_no_conform_provided_deep(loops):
+    return _bench_iface_call_simple(loops, DeepestInheritance())
+
+
+runner = pyperf.Runner()
+
+runner.bench_time_func(
+    'call interface (provides; deep)',
+    bench_iface_call_no_conform_provided_deep,
+    inner_loops=INNER * len(ifaces)
+)
+
+runner.bench_time_func(
+    'call interface (provides; wide)',
+    bench_iface_call_no_conform_provided_wide,
+    inner_loops=INNER * len(ifaces)
+)

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/doctest Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/doctest/output.txt Added

@@ -0,0 +1,65 @@
+Results of doctest builder run on 2022-11-03 13:55:30
+=====================================================
+
+Document: api/specifications
+----------------------------
+1 items passed all tests:
+ 109 tests in default
+109 tests in 1 items.
+109 passed and 0 failed.
+Test passed.
+
+Document: verify
+----------------
+1 items passed all tests:
+  78 tests in default
+78 tests in 1 items.
+78 passed and 0 failed.
+Test passed.
+
+Document: human
+---------------
+1 items passed all tests:
+  18 tests in default
+18 tests in 1 items.
+18 passed and 0 failed.
+Test passed.
+
+Document: api/declarations
+--------------------------
+1 items passed all tests:
+ 302 tests in default
+302 tests in 1 items.
+302 passed and 0 failed.
+Test passed.
+
+Document: adapter
+-----------------
+1 items passed all tests:
+ 164 tests in default
+164 tests in 1 items.
+164 passed and 0 failed.
+Test passed.
+
+Document: README
+----------------
+1 items passed all tests:
+ 218 tests in default
+218 tests in 1 items.
+218 passed and 0 failed.
+Test passed.
+
+Document: foodforthought
+------------------------
+1 items passed all tests:
+  25 tests in default
+25 tests in 1 items.
+25 passed and 0 failed.
+Test passed.
+
+Doctest summary
+===============
+  914 tests
+    0 failures in tests
+    0 failures in setup code
+    0 failures in cleanup code

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/README.rst.txt Added

@@ -0,0 +1,1357 @@
+============
+ Interfaces
+============
+
+.. currentmodule:: zope.interface
+
+Interfaces are objects that specify (document) the external behavior
+of objects that "provide" them.  An interface specifies behavior
+through:
+
+- Informal documentation in a doc string
+
+- Attribute definitions
+
+- Invariants, which are conditions that must hold for objects that
+  provide the interface
+
+Attribute definitions specify specific attributes. They define the
+attribute name and provide documentation and constraints of attribute
+values.  Attribute definitions can take a number of forms, as we'll
+see below.
+
+Defining interfaces
+===================
+
+Interfaces are defined using Python ``class`` statements:
+
+.. doctest::
+
+  >>> import zope.interface
+  >>> class IFoo(zope.interface.Interface):
+  ...    """Foo blah blah"""
+  ...
+  ...    x = zope.interface.Attribute("""X blah blah""")
+  ...
+  ...    def bar(q, r=None):
+  ...        """bar blah blah"""
+
+In the example above, we've created an interface, :class:`IFoo`.  We
+subclassed :class:`zope.interface.Interface`, which is an ancestor interface for
+all interfaces, much as ``object`` is an ancestor of all new-style
+classes #create_.   The interface is not a class, it's an Interface,
+an instance of :class:`zope.interface.interface.InterfaceClass`:
+
+.. doctest::
+
+  >>> type(IFoo)
+  <class 'zope.interface.interface.InterfaceClass'>
+
+We can ask for the interface's documentation:
+
+.. doctest::
+
+  >>> IFoo.__doc__
+  'Foo blah blah'
+
+and its name:
+
+.. doctest::
+
+  >>> IFoo.__name__
+  'IFoo'
+
+and even its module:
+
+.. doctest::
+
+  >>> IFoo.__module__
+  'builtins'
+
+The interface defined two attributes:
+
+``x``
+  This is the simplest form of attribute definition.  It has a name
+  and a doc string.  It doesn't formally specify anything else.
+
+``bar``
+  This is a method.  A method is defined via a function definition.  A
+  method is simply an attribute constrained to be a callable with a
+  particular signature, as provided by the function definition.
+
+  Note that ``bar`` doesn't take a ``self`` argument.  Interfaces document
+  how an object is *used*.  When calling instance methods, you don't
+  pass a ``self`` argument, so a ``self`` argument isn't included in the
+  interface signature.  The ``self`` argument in instance methods is
+  really an implementation detail of Python instances. Other objects,
+  besides instances can provide interfaces and their methods might not
+  be instance methods. For example, modules can provide interfaces and
+  their methods are usually just functions.  Even instances can have
+  methods that are not instance methods.
+
+You can access the attributes defined by an interface using mapping
+syntax:
+
+.. doctest::
+
+  >>> x = IFoo'x'
+  >>> type(x)
+  <class 'zope.interface.interface.Attribute'>
+  >>> x.__name__
+  'x'
+  >>> x.__doc__
+  'X blah blah'
+
+  >>> IFoo.get('x').__name__
+  'x'
+
+  >>> IFoo.get('y')
+
+You can use ``in`` to determine if an interface defines a name:
+
+.. doctest::
+
+  >>> 'x' in IFoo
+  True
+
+You can iterate over interfaces to get the names they define:
+
+.. doctest::
+
+  >>> names = list(IFoo)
+  >>> names.sort()
+  >>> names
+  'bar', 'x'
+
+Remember that interfaces aren't classes. You can't access attribute
+definitions as attributes of interfaces:
+
+.. doctest::
+
+  >>> IFoo.x
+  Traceback (most recent call last):
+    File "<stdin>", line 1, in ?
+  AttributeError: 'InterfaceClass' object has no attribute 'x'
+
+Methods provide access to the method signature:
+
+.. doctest::
+
+  >>> bar = IFoo'bar'
+  >>> bar.getSignatureString()
+  '(q, r=None)'
+
+TODO
+  Methods really should have a better API.  This is something that
+  needs to be improved.
+
+Declaring interfaces
+====================
+
+Having defined interfaces, we can *declare* that objects provide
+them.  Before we describe the details, lets define some terms:
+
+*provide*
+   We say that objects *provide* interfaces.  If an object provides an
+   interface, then the interface specifies the behavior of the
+   object. In other words, interfaces specify the behavior of the
+   objects that provide them.
+
+*implement*
+   We normally say that classes *implement* interfaces.  If a class
+   implements an interface, then the instances of the class provide
+   the interface.  Objects provide interfaces that their classes
+   implement #factory_.  (Objects can provide interfaces directly,
+   in addition to what their classes implement.)
+
+   It is important to note that classes don't usually provide the
+   interfaces that they implement.
+
+   We can generalize this to factories.  For any callable object we
+   can declare that it produces objects that provide some interfaces
+   by saying that the factory implements the interfaces.
+
+Now that we've defined these terms, we can talk about the API for
+declaring interfaces.
+
+Declaring implemented interfaces
+--------------------------------
+
+The most common way to declare interfaces is using the `implementer`
+decorator on a class:
+
+.. doctest::
+
+  >>> @zope.interface.implementer(IFoo)
+  ... class Foo:
+  ...
+  ...     def __init__(self, x=None):
+  ...         self.x = x
+  ...
+  ...     def bar(self, q, r=None):
+  ...         return q, r, self.x
+  ...
+  ...     def __repr__(self):
+  ...         return "Foo(%s)" % self.x
+
+
+In this example, we declared that ``Foo`` implements ``IFoo``. This means
+that instances of ``Foo`` provide ``IFoo``.  Having made this declaration,

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/README.ru.rst.txt Added

@@ -0,0 +1,804 @@
+==========
+Интерфейсы
+==========
+
+.. contents::
+
+Интерфейсы - это объекты специфицирующие (документирующие) внешнее поведение
+объектов которые их "предоставляют". Интерфейсы определяют поведение через
+следующие составляющие:
+
+- Неформальную документацию в строках документации
+
+- Определения атрибутов
+
+- Инварианты - условия, которые должны соблюдаться для объектов предоставляющих
+  интерфейс
+
+Определения атрибутов описывают конкретные атрибуты. Они определяют
+имя атрибута и предоставляют документацию и ограничения для значений
+атрибута. Определения атрибутов могут быть заданы несколькими путями
+как мы увидим ниже.
+
+Определение интерфейсов
+=======================
+
+Интерфейсы определяются с использованием ключевого слова class::
+
+  >>> import zope.interface
+  >>> class IFoo(zope.interface.Interface):
+  ...    """Foo blah blah"""
+  ...
+  ...    x = zope.interface.Attribute("""X blah blah""")
+  ...
+  ...    def bar(q, r=None):
+  ...        """bar blah blah"""
+
+В примере выше мы создали интерфейс `IFoo`. Мы наследуем его от
+класса `zope.interface.Interface`, который является родительским интерфейсом
+для всех интерфейсов, как `object` - это родительский класс для всех новых
+классов #create_. Данный интерфейс не является классом, а является
+Интерфейсом, экземпляром `InterfaceClass`::
+
+  >>> type(IFoo)
+  <class 'zope.interface.interface.InterfaceClass'>
+
+Мы можем запросить у интерфейса его документацию::
+
+  >>> IFoo.__doc__
+  'Foo blah blah'
+
+и его имя::
+
+  >>> IFoo.__name__
+  'IFoo'
+
+и даже модуль в котором он определен::
+
+  >>> IFoo.__module__
+  '__main__'
+
+Наш интерфейс определяет два атрибута:
+
+`x`
+  Это простейшая форма определения атрибутов. Определяются имя
+  и строка документации. Формально здесь не определяется ничего более.
+
+`bar`
+  Это метод. Методы определяются как обычные функции. Метод - это просто
+  атрибут который должен быть вызываемым с указанием сигнатуры,
+  предоставляемой определением функции.
+
+  Надо отметить, что аргумент `self` не указывается для `bar`. Интерфейс
+  документирует как объект *используется*. Когда методы экземпляров классов
+  вызываются мы не передаем аргумент `self`, таким образом аргумент `self`
+  не включается и в сигнатуру интерфейса. Аргумент `self` в методах
+  экземпляров классов на самом деле деталь реализации экземпляров классов
+  в Python. Другие объекты кроме экземпляров классов могут предоставлять
+  интерфейсы и их методы могут не быть методами экземпляров классов. Для
+  примера модули могут предоставлять интерфейсы и их методы обычно просто
+  функции. Даже экземпляры могут иметь методы не являющиеся методами
+  экземпляров класса.
+
+Мы можем получить доступ к атрибутам определенным интерфейсом используя
+синтаксис доступа к элементам массива::
+
+  >>> x = IFoo'x'
+  >>> type(x)
+  <class 'zope.interface.interface.Attribute'>
+  >>> x.__name__
+  'x'
+  >>> x.__doc__
+  'X blah blah'
+
+  >>> IFoo.get('x').__name__
+  'x'
+
+  >>> IFoo.get('y')
+
+Можно использовать `in` для определения содержит ли интерфейс
+определенное имя::
+
+  >>> 'x' in IFoo
+  True
+
+Мы можем использовать итератор для интерфейсов чтобы получить все имена
+которые интерфейсы определяют::
+
+  >>> names = list(IFoo)
+  >>> names.sort()
+  >>> names
+  'bar', 'x'
+
+Надо помнить, что интерфейсы не являются классами. Мы не можем получить
+доступ к определениям атрибутов через доступ к атрибутам интерфейсов::
+
+  >>> IFoo.x
+  Traceback (most recent call last):
+    File "<stdin>", line 1, in ?
+  AttributeError: 'InterfaceClass' object has no attribute 'x'
+
+Методы также предоставляют доступ к сигнатуре метода::
+
+  >>> bar = IFoo'bar'
+  >>> bar.getSignatureString()
+  '(q, r=None)'
+
+Объявление интерфейсов
+======================
+
+Определив интерфейс мы можем теперь *объявить*, что объекты предоставляют их.
+Перед описанием деталей определим некоторые термины:
+
+*предоставлять*
+  Мы говорим, что объекты *предоставляют* интерфейсы. Если объект
+  предоставляет интерфейс, тогда интерфейс специфицирует поведение объекта.
+  Другими словами, интерфейсы специфицируют поведение объектов которые
+  предоставляют их.
+
+*реализовать*
+  Мы обычно говорим что классы *реализуют* интерфейсы. Если класс
+  реализует интерфейс, тогда экземпляры этого класса предоставляют
+  данный интерфейс. Объекты предоставляют интерфейсы которые их классы
+  реализуют #factory_. (Объекты также могут предоставлять интерфейсы напрямую
+  плюс к тем которые реализуют их классы.)
+
+  Важно помнить, что классы обычно не предоставляют интерфейсы которые
+  они реализуют.
+
+  Мы можем обобщить это до фабрик. Для любого вызываемого объекта мы можем
+  объявить что он производит объекты которые предоставляют какие-либо
+  интерфейсы сказав, что фабрика реализует данные интерфейсы.
+
+Теперь после того как мы определили эти термины мы можем поговорить об
+API для объявления интерфейсов.
+
+Объявление реализуемых интерфейсов
+----------------------------------
+
+Наиболее часто используемый путь для объявления интерфейсов - это использование
+функции implements в определении класса::
+
+  >>> class Foo:
+  ...     zope.interface.implements(IFoo)
+  ...
+  ...     def __init__(self, x=None):
+  ...         self.x = x
+  ...
+  ...     def bar(self, q, r=None):
+  ...         return q, r, self.x
+  ...
+  ...     def __repr__(self):
+  ...         return "Foo(%s)" % self.x
+
+В этом примере мы объявили, что `Foo` реализует `IFoo`. Это значит, что
+экземпляры `Foo` предоставляют `IFoo`. После данного объявления есть
+несколько путей для анализа объявлений. Во-первых мы можем спросить
+что интерфейс реализован классом::
+
+  >>> IFoo.implementedBy(Foo)
+  True
+
+Также мы можем спросить если интерфейс предоставляется объектами класса::
+
+  >>> foo = Foo()
+  >>> IFoo.providedBy(foo)
+  True
+
+Конечно `Foo` не предоставляет `IFoo`, он реализует его::
+
+  >>> IFoo.providedBy(Foo)
+  False
+
+Мы можем также узнать какие интерфейсы реализуются объектами::
+
+  >>> list(zope.interface.implementedBy(Foo))
+  <InterfaceClass __main__.IFoo>
+
+Это ошибка спрашивать про интерфейсы реализуемые не вызываемым объектом::
+

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/adapter.rst.txt Added

@@ -0,0 +1,690 @@
+.. _adapter-registry:
+
+==================
+ Adapter Registry
+==================
+
+Adapter registries provide a way to register objects that depend on
+one or more interface specifications and provide (perhaps indirectly)
+some interface.  In addition, the registrations have names. (You can
+think of the names as qualifiers of the provided interfaces.)
+
+The term "interface specification" refers both to interfaces and to
+interface declarations, such as declarations of interfaces implemented
+by a class.
+
+
+Single Adapters
+===============
+
+Let's look at a simple example, using a single required specification:
+
+.. doctest::
+
+  >>> from zope.interface.adapter import AdapterRegistry
+  >>> import zope.interface
+
+  >>> class IRequireBase(zope.interface.Interface):
+  ...     pass
+  >>> class IProvideBase(zope.interface.Interface):
+  ...     pass
+  >>> class IProvideChild(IProvideBase):
+  ...     pass
+
+  >>> registry = AdapterRegistry()
+
+We'll register an object that depends on ``IRequireBase`` and "provides" ``IProvideChild``:
+
+.. doctest::
+
+  >>> registry.register(IRequireBase, IProvideChild, '', 'Base->Child')
+
+Given the registration, we can look it up again:
+
+.. doctest::
+
+  >>> registry.lookup(IRequireBase, IProvideChild, '')
+  'Base->Child'
+
+Note that we used an integer in the example.  In real applications,
+one would use some objects that actually depend on or provide
+interfaces. The registry doesn't care about what gets registered, so
+we'll use integers and strings to keep the examples simple. There is
+one exception.  Registering a value of ``None`` unregisters any
+previously-registered value.
+
+If an object depends on a specification, it can be looked up with a
+specification that extends the specification that it depends on:
+
+.. doctest::
+
+  >>> class IRequireChild(IRequireBase):
+  ...     pass
+  >>> registry.lookup(IRequireChild, IProvideChild, '')
+  'Base->Child'
+
+We can use a class implementation specification to look up the object:
+
+.. doctest::
+
+  >>> @zope.interface.implementer(IRequireChild)
+  ... class C2:
+  ...     pass
+
+  >>> registry.lookup(zope.interface.implementedBy(C2), IProvideChild, '')
+  'Base->Child'
+
+
+and it can be looked up for interfaces that its provided interface
+extends:
+
+.. doctest::
+
+  >>> registry.lookup(IRequireBase, IProvideBase, '')
+  'Base->Child'
+  >>> registry.lookup(IRequireChild, IProvideBase, '')
+  'Base->Child'
+
+But if you require a specification that doesn't extend the specification the
+object depends on, you won't get anything:
+
+.. doctest::
+
+  >>> registry.lookup(zope.interface.Interface, IProvideBase, '')
+
+By the way, you can pass a default value to lookup:
+
+.. doctest::
+
+  >>> registry.lookup(zope.interface.Interface, IProvideBase, '', 42)
+  42
+
+If you try to get an interface the object doesn't provide, you also
+won't get anything:
+
+.. doctest::
+
+  >>> class IProvideGrandchild(IProvideChild):
+  ...     pass
+  >>> registry.lookup(IRequireBase, IProvideGrandchild, '')
+
+You also won't get anything if you use the wrong name:
+
+.. doctest::
+
+  >>> registry.lookup(IRequireBase, IProvideBase, 'bob')
+  >>> registry.register(IRequireBase, IProvideChild, 'bob', "Bob's 12")
+  >>> registry.lookup(IRequireBase, IProvideBase, 'bob')
+  "Bob's 12"
+
+You can leave the name off when doing a lookup:
+
+.. doctest::
+
+  >>> registry.lookup(IRequireBase, IProvideBase)
+  'Base->Child'
+
+If we register an object that provides ``IProvideBase``:
+
+.. doctest::
+
+  >>> registry.register(IRequireBase, IProvideBase, '', 'Base->Base')
+
+then that object will be preferred over ``O('Base->Child')``:
+
+.. doctest::
+
+  >>> registry.lookup(IRequireBase, IProvideBase, '')
+  'Base->Base'
+
+Also, if we register an object for ``IRequireChild``, then that will be preferred
+when using ``IRequireChild``:
+
+.. doctest::
+
+  >>> registry.register(IRequireChild, IProvideBase, '', 'Child->Base')
+  >>> registry.lookup(IRequireChild, IProvideBase, '')
+  'Child->Base'
+
+Finding out what, if anything, is registered
+--------------------------------------------
+
+We can ask if there is an adapter registered for a collection of
+interfaces. This is different than lookup, because it looks for an
+exact match:
+
+.. doctest::
+
+  >>> print(registry.registered(IRequireBase, IProvideBase))
+  Base->Base
+
+  >>> print(registry.registered(IRequireBase, IProvideChild))
+  Base->Child
+
+  >>> print(registry.registered(IRequireBase, IProvideChild, 'bob'))
+  Bob's 12
+
+
+  >>> print(registry.registered(IRequireChild, IProvideBase))
+  Child->Base
+
+  >>> print(registry.registered(IRequireChild, IProvideChild))
+  None
+
+In the last example, ``None`` was returned because nothing was registered
+exactly for the given interfaces.
+
+lookup1
+-------
+
+Lookup of single adapters is common enough that there is a specialized
+version of lookup that takes a single required interface:
+
+.. doctest::
+
+  >>> registry.lookup1(IRequireChild, IProvideBase, '')
+  'Child->Base'
+  >>> registry.lookup1(IRequireChild, IProvideBase)
+  'Child->Base'
+
+Actual Adaptation
+-----------------
+
+The adapter registry is intended to support adaptation, where one
+object that implements an interface is adapted to another object that
+supports a different interface.  The adapter registry supports the
+computation of adapters. In this case, we have to register adapter
+factories:
+
+.. doctest::

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/adapter.ru.rst.txt Added

@@ -0,0 +1,540 @@
+================
+Реестр адаптеров
+================
+
+.. contents::
+
+Реестры адаптеров предоставляют возможность для регистрации объектов которые
+зависят от одной, или нескольких спецификаций интерфейсов и предоставляют
+(возможно не напрямую) какой-либо интерфейс. В дополнение, регистрации имеют
+имена. (Можно думать об именах как о спецификаторах предоставляемого
+интерфейса.)
+
+Термин "спецификация интерфейса" ссылается и на интерфейсы и на определения
+интерфейсов, такие как определения интерфейсов реализованных некоторым классом.
+
+Одиночные адаптеры
+==================
+
+Давайте рассмотрим простой пример использующий единственную требуемую
+спецификацию::
+
+  >>> from zope.interface.adapter import AdapterRegistry
+  >>> import zope.interface
+
+  >>> class IR1(zope.interface.Interface):
+  ...     pass
+  >>> class IP1(zope.interface.Interface):
+  ...     pass
+  >>> class IP2(IP1):
+  ...     pass
+
+  >>> registry = AdapterRegistry()
+
+Мы зарегистрируем объект который зависит от IR1 и "предоставляет" IP2::
+
+  >>> registry.register(IR1, IP2, '', 12)
+
+После регистрации мы можем запросить объект снова::
+
+  >>> registry.lookup(IR1, IP2, '')
+  12
+
+Заметьте, что мы используем целое в этом примере. В реальных приложениях вы
+можете использовать объекты которые на самом деле зависят или предоставляют
+интерфейсы. Реестр не заботиться о том, что регистрируется и таким образом мы
+можем использовать целые, или строки что бы упростить наши примеры. Здесь есть
+одно исключение. Регистрация значения None удаляет регистрацию для любого
+зарегистрированного прежде значения.
+
+Если объект зависит от спецификации он может быть запрошен с помощью
+спецификации которая расширяет спецификацию от которой он зависит::
+
+  >>> class IR2(IR1):
+  ...     pass
+  >>> registry.lookup(IR2, IP2, '')
+  12
+
+Мы можем использовать класс реализующий спецификацию для запроса объекта::
+
+  >>> class C2:
+  ...     zope.interface.implements(IR2)
+
+  >>> registry.lookup(zope.interface.implementedBy(C2), IP2, '')
+  12
+
+и объект может быть запрошен для интерфейсов которые предоставляемый объектом
+интерфейс расширяет::
+
+  >>> registry.lookup(IR1, IP1, '')
+  12
+  >>> registry.lookup(IR2, IP1, '')
+  12
+
+Но если вы требуете спецификацию которая не расширяет спецификацию от которой
+зависит объект, вы не получите ничего::
+
+  >>> registry.lookup(zope.interface.Interface, IP1, '')
+
+Между прочим, вы можете передать значение по умолчанию при запросе::
+
+  >>> registry.lookup(zope.interface.Interface, IP1, '', 42)
+  42
+
+Если вы пробуете получить интерфейс который объект не предоставляет вы также
+не получите ничего::
+
+  >>> class IP3(IP2):
+  ...     pass
+  >>> registry.lookup(IR1, IP3, '')
+
+Вы также не получите ничего если вы используете неверное имя::
+
+  >>> registry.lookup(IR1, IP1, 'bob')
+  >>> registry.register(IR1, IP2, 'bob', "Bob's 12")
+  >>> registry.lookup(IR1, IP1, 'bob')
+  "Bob's 12"
+
+Вы можете не использовать имя при запросе::
+
+  >>> registry.lookup(IR1, IP1)
+  12
+
+Если мы регистрируем объект который предоставляет IP1::
+
+  >>> registry.register(IR1, IP1, '', 11)
+
+тогда этот объект будет иметь преимущество перед O(12)::
+
+  >>> registry.lookup(IR1, IP1, '')
+  11
+
+Также, если мы регистрируем объект для IR2 тогда он будет иметь преимущество
+когда используется IR2::
+
+  >>> registry.register(IR2, IP1, '', 21)
+  >>> registry.lookup(IR2, IP1, '')
+  21
+
+Поиск того, что (если вообще что-то) зарегистрировано
+-----------------------------------------------------
+
+Мы можем спросить есть-ли адаптер зарегистрированный для набора интерфейсов.
+Это отличается от обычного запроса так как здесь мы ищем точное совпадение::
+
+  >>> print registry.registered(IR1, IP1)
+  11
+
+  >>> print registry.registered(IR1, IP2)
+  12
+
+  >>> print registry.registered(IR1, IP2, 'bob')
+  Bob's 12
+  
+
+  >>> print registry.registered(IR2, IP1)
+  21
+
+  >>> print registry.registered(IR2, IP2)
+  None
+
+В последнем примере, None был возвращен потому, что для данного интерфейса
+ничего не было зарегистрировано.
+
+lookup1
+-------
+
+Запрос одиночного адаптера - это наиболее частая операция и для нее есть
+специализированная версия запроса которая получает на вход единственный
+требуемый интерфейс::
+
+  >>> registry.lookup1(IR2, IP1, '')
+  21
+  >>> registry.lookup1(IR2, IP1)
+  21
+
+Адаптация на практике
+---------------------
+
+Реестр адаптеров предназначен для поддержки адаптации когда один объект
+реализующий интерфейс адаптируется к другому объекту который поддерживает
+другой интерфейс. Реестр адаптеров также поддерживает вычисление адаптеров. В
+этом случае мы должны регистрировать фабрики для адаптеров::
+
+   >>> class IR(zope.interface.Interface):
+   ...     pass
+
+   >>> class X:
+   ...     zope.interface.implements(IR)
+           
+   >>> class Y:
+   ...     zope.interface.implements(IP1)
+   ...     def __init__(self, context):
+   ...         self.context = context
+
+  >>> registry.register(IR, IP1, '', Y)
+
+В этом случае мы регистрируем класс как фабрику. Теперь мы можем вызвать
+`queryAdapter` для получения адаптированного объекта::
+
+  >>> x = X()
+  >>> y = registry.queryAdapter(x, IP1)
+  >>> y.__class__.__name__
+  'Y'
+  >>> y.context is x
+  True
+
+Мы также можем регистрировать и запрашивать по имени::
+
+  >>> class Y2(Y):
+  ...     pass
+
+  >>> registry.register(IR, IP1, 'bob', Y2)
+  >>> y = registry.queryAdapter(x, IP1, 'bob')
+  >>> y.__class__.__name__
+  'Y2'
+  >>> y.context is x
+  True
+
+Когда фабрика для адаптера возвращает `None` - это рассматривается как если бы

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/adapters.rst.txt Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/common.rst.txt Added

@@ -0,0 +1,50 @@
+====================================
+ Python Standard Library Interfaces
+====================================
+
+The ``zope.interface.common`` package provides interfaces for objects
+distributed as part of the Python standard library. Importing these
+modules (usually) has the effect of making the standard library objects
+implement the correct interface.
+
+zope.interface.common.interface
+===============================
+
+.. automodule:: zope.interface.common.interfaces
+
+zope.interface.common.idatetime
+===============================
+
+.. automodule:: zope.interface.common.idatetime
+
+zope.interface.common.collections
+=================================
+
+.. automodule:: zope.interface.common.collections
+
+zope.interface.common.numbers
+=============================
+
+.. automodule:: zope.interface.common.numbers
+
+zope.interface.common.builtins
+==============================
+
+.. automodule:: zope.interface.common.builtins
+
+zope.interface.common.io
+========================
+
+.. automodule:: zope.interface.common.io
+
+.. Deprecated or discouraged modules below this
+
+zope.interface.common.mapping
+=============================
+
+.. automodule:: zope.interface.common.mapping
+
+zope.interface.common.sequence
+==============================
+
+.. automodule:: zope.interface.common.sequence

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/components.rst.txt Added

@@ -0,0 +1,84 @@
+======================
+ Component Registries
+======================
+
+The component registry's API is defined by
+``zope.interface.interfaces.IComponents``:
+
+.. autointerface:: zope.interface.interfaces.IComponentLookup
+   :members:
+   :member-order: bysource
+
+
+.. autointerface:: zope.interface.interfaces.IComponentRegistry
+   :members:
+   :member-order: bysource
+
+.. autointerface:: zope.interface.interfaces.IComponents
+   :members:
+   :member-order: bysource
+
+One default implementation of `~zope.interface.interfaces.IComponents` is provided.
+
+.. autoclass:: zope.interface.registry.Components
+
+Events
+======
+
+Adding and removing components from the component registry create
+registration and unregistration events. Like most things, they are
+defined by an interface and a default implementation is provided.
+
+Registration
+------------
+
+.. autointerface:: zope.interface.interfaces.IObjectEvent
+.. autointerface:: zope.interface.interfaces.IRegistrationEvent
+
+.. autointerface:: zope.interface.interfaces.IRegistered
+.. autoclass:: zope.interface.interfaces.Registered
+
+.. autointerface:: zope.interface.interfaces.IUnregistered
+.. autoclass:: zope.interface.interfaces.Unregistered
+
+
+Details
+-------
+
+These are all types of ``IObjectEvent``, meaning they have an object
+that provides specific details about the event. Component registries
+create detail objects for four types of components they manage.
+
+All four share a common base interface.
+
+.. autointerface:: zope.interface.interfaces.IRegistration
+
+* Utilities
+
+  .. autointerface:: zope.interface.interfaces.IUtilityRegistration
+  .. autoclass:: zope.interface.registry.UtilityRegistration
+
+* Handlers
+
+  .. autointerface:: zope.interface.interfaces.IHandlerRegistration
+  .. autoclass:: zope.interface.registry.HandlerRegistration
+
+* Adapters
+
+  For ease of implementation, a shared base class is used for these
+  events. It should not be referenced by clients, but it is documented
+  to show the common attributes.
+
+  .. autointerface:: zope.interface.interfaces._IBaseAdapterRegistration
+
+  .. autointerface:: zope.interface.interfaces.IAdapterRegistration
+  .. autoclass:: zope.interface.registry.AdapterRegistration
+
+  .. autointerface:: zope.interface.interfaces.ISubscriptionAdapterRegistration
+  .. autoclass:: zope.interface.registry.SubscriptionRegistration
+
+Exceptions
+==========
+
+.. autoclass:: zope.interface.interfaces.ComponentLookupError
+.. autoclass:: zope.interface.interfaces.Invalid

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/declarations.rst.txt Added

@@ -0,0 +1,975 @@
+==================================================
+ Declaring and Checking The Interfaces of Objects
+==================================================
+
+Declaring what interfaces an object implements or provides, and later
+being able to check those, is an important part of this package.
+Declaring interfaces, in particular, can be done both statically at
+object definition time and dynamically later on.
+
+The functionality that allows declaring and checking interfaces is
+provided directly in the ``zope.interface`` module. It is described by
+the interface ``zope.interface.interfaces.IInterfaceDeclaration``. We
+will first look at that interface, and then we will look more
+carefully at each object it documents, including providing examples.
+
+.. autointerface:: zope.interface.interfaces.IInterfaceDeclaration
+
+
+.. currentmodule:: zope.interface
+
+Declaring Interfaces
+====================
+
+To declare an interface itself, extend the ``Interface`` base class.
+
+.. autointerface:: Interface
+   :noindex:
+
+.. autofunction:: taggedValue
+   :noindex:
+
+   .. documented more thoroughly in README.rst
+
+.. autofunction:: invariant
+   :noindex:
+
+   .. documented in README.rst
+
+.. autofunction:: interfacemethod
+
+Declaring The Interfaces of Objects
+===================================
+
+
+implementer
+-----------
+
+.. autoclass:: implementer
+
+
+implementer_only
+----------------
+
+.. autoclass:: implementer_only
+
+
+classImplementsOnly
+-------------------
+
+.. autofunction:: classImplementsOnly
+
+
+Consider the following example:
+
+.. doctest::
+
+   >>> from zope.interface import implementedBy
+   >>> from zope.interface import implementer
+   >>> from zope.interface import classImplementsOnly
+   >>> from zope.interface import Interface
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(Interface): pass
+   ...
+   >>> class I3(Interface): pass
+   ...
+   >>> class I4(Interface): pass
+   ...
+   >>> @implementer(I3)
+   ... class A(object):
+   ...     pass
+   >>> @implementer(I4)
+   ... class B(object):
+   ...     pass
+   >>> class C(A, B):
+   ...   pass
+   >>> classImplementsOnly(C, I1, I2)
+   >>> i.getName() for i in implementedBy(C)
+   'I1', 'I2'
+
+Instances of ``C`` provide only ``I1``, ``I2``, and regardless of
+whatever interfaces instances of ``A`` and ``B`` implement.
+
+
+classImplements
+---------------
+
+.. autofunction:: classImplements
+
+Consider the following example:
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> from zope.interface import classImplements
+   >>> from zope.interface.ro import is_consistent
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(Interface): pass
+   ...
+   >>> class IA(Interface): pass
+   ...
+   >>> class IB(Interface): pass
+   ...
+   >>> class I5(Interface): pass
+   ...
+   >>> @implementer(IA)
+   ... class A(object):
+   ...     pass
+   >>> @implementer(IB)
+   ... class B(object):
+   ...     pass
+   >>> class C(A, B):
+   ...   pass
+   >>> classImplements(C, I1, I2)
+   >>> i.getName() for i in implementedBy(C)
+   'I1', 'I2', 'IA', 'IB'
+
+Instances of ``C`` provide ``I1`` and ``I2``, plus whatever
+instances of ``A`` and ``B`` provide.
+
+.. doctest::
+
+   >>> classImplements(C, I5)
+   >>> i.getName() for i in implementedBy(C)
+   'I1', 'I2', 'I5', 'IA', 'IB'
+
+Instances of ``C`` now also provide ``I5``. Notice how ``I5`` was
+added to the *end* of the list of things provided directly by ``C``.
+
+If we ask a class to implement an interface that extends
+an interface it already implements, that interface will go at the
+*beginning* of the list, in order to preserve a consistent resolution
+order.
+
+.. doctest::
+
+   >>> class I6(I5): pass
+   >>> class I7(IA): pass
+   >>> classImplements(C, I6, I7)
+   >>> i.getName() for i in implementedBy(C)
+   'I6', 'I1', 'I2', 'I5', 'I7', 'IA', 'IB'
+   >>> is_consistent(implementedBy(C))
+   True
+
+This cannot be used to introduce duplicates.
+
+.. doctest::
+
+   >>> classImplements(C, IA, IB, I1, I2)
+   >>> i.getName() for i in implementedBy(C)
+   'I6', 'I1', 'I2', 'I5', 'I7', 'IA', 'IB'
+
+
+classImplementsFirst
+--------------------
+
+.. autofunction:: classImplementsFirst
+
+Consider the following example:
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> from zope.interface import classImplements
+   >>> from zope.interface import classImplementsFirst
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(Interface): pass
+   ...
+   >>> class IA(Interface): pass
+   ...
+   >>> class IB(Interface): pass
+   ...
+   >>> class I5(Interface): pass
+   ...
+   >>> @implementer(IA)
+   ... class A(object):
+   ...     pass
+   >>> @implementer(IB)
+   ... class B(object):
+   ...     pass
+   >>> class C(A, B):
+   ...   pass
+   >>> classImplementsFirst(C, I2)
+   >>> classImplementsFirst(C, I1)
+   >>> i.getName() for i in implementedBy(C)
+   'I1', 'I2', 'IA', 'IB'
+

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/index.rst.txt Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/ro.rst.txt Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/api/specifications.rst.txt Added

@@ -0,0 +1,380 @@
+==========================
+ Interface Specifications
+==========================
+
+.. currentmodule:: zope.interface.interfaces
+
+
+This document discusses the actual interface objects themselves. We
+begin with a basic concept of specifying an object's behaviour (with
+an `ISpecification`), and then we describe the way we write such a
+specification (`IInterface`). Combinations of specifications (e.g., an
+object that provides multiple interfaces) are covered by
+`IDeclaration`.
+
+Specification
+=============
+
+Specification objects implement the API defined by
+:class:`ISpecification`:
+
+.. autointerface:: ISpecification
+   :members:
+   :member-order: bysource
+
+.. autoclass:: zope.interface.interface.Specification
+   :no-members:
+
+For example:
+
+.. doctest::
+
+   >>> from zope.interface.interface import Specification
+   >>> from zope.interface import Interface
+   >>> class I1(Interface):
+   ...     pass
+   >>> class I2(I1):
+   ...     pass
+   >>> class I3(I2):
+   ...     pass
+   >>> i.__name__ for i in I1.__bases__
+   'Interface'
+   >>> i.__name__ for i in I2.__bases__
+   'I1'
+   >>> I3.extends(I1)
+   True
+   >>> I2.__bases__ = (Interface, )
+   >>> i.__name__ for i in I2.__bases__
+   'Interface'
+   >>> I3.extends(I1)
+   False
+
+Exmples for :meth:`.Specification.providedBy`:
+
+.. doctest::
+
+   >>> from zope.interface import *
+   >>> class I1(Interface):
+   ...     pass
+   >>> @implementer(I1)
+   ... class C(object):
+   ...     pass
+   >>> c = C()
+   >>> class X(object):
+   ...     pass
+   >>> x = X()
+   >>> I1.providedBy(x)
+   False
+   >>> I1.providedBy(C)
+   False
+   >>> I1.providedBy(c)
+   True
+   >>> directlyProvides(x, I1)
+   >>> I1.providedBy(x)
+   True
+   >>> directlyProvides(C, I1)
+   >>> I1.providedBy(C)
+   True
+
+Examples for :meth:`.Specification.isOrExtends`:
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> from zope.interface.declarations import Declaration
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(I1): pass
+   ...
+   >>> class I3(Interface): pass
+   ...
+   >>> class I4(I3): pass
+   ...
+   >>> spec = Declaration()
+   >>> int(spec.extends(Interface))
+   1
+   >>> spec = Declaration(I2)
+   >>> int(spec.extends(Interface))
+   1
+   >>> int(spec.extends(I1))
+   1
+   >>> int(spec.extends(I2))
+   1
+   >>> int(spec.extends(I3))
+   0
+   >>> int(spec.extends(I4))
+   0
+
+Examples for :meth:`.Specification.interfaces`:
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(I1): pass
+   ...
+   >>> class I3(Interface): pass
+   ...
+   >>> class I4(I3): pass
+   ...
+   >>> spec = Specification((I2, I3))
+   >>> spec = Specification((I4, spec))
+   >>> i = spec.interfaces()
+   >>> x.getName() for x in i
+   'I4', 'I2', 'I3'
+   >>> list(i)
+   
+
+Exmples for :meth:`.Specification.extends`:
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> from zope.interface.declarations import Declaration
+   >>> class I1(Interface): pass
+   ...
+   >>> class I2(I1): pass
+   ...
+   >>> class I3(Interface): pass
+   ...
+   >>> class I4(I3): pass
+   ...
+   >>> spec = Declaration()
+   >>> int(spec.extends(Interface))
+   1
+   >>> spec = Declaration(I2)
+   >>> int(spec.extends(Interface))
+   1
+   >>> int(spec.extends(I1))
+   1
+   >>> int(spec.extends(I2))
+   1
+   >>> int(spec.extends(I3))
+   0
+   >>> int(spec.extends(I4))
+   0
+   >>> I2.extends(I2)
+   False
+   >>> I2.extends(I2, False)
+   True
+   >>> I2.extends(I2, strict=False)
+   True
+
+.. _spec_eq_hash:
+
+Equality, Hashing, and Comparisons
+----------------------------------
+
+Specifications (including their notable subclass `Interface`), are
+hashed and compared (sorted) based solely on their ``__name__`` and
+``__module__``, not including any information about their enclosing
+scope, if any (e.g., their ``__qualname__``). This means that any two
+objects created with the same name and module are considered equal and
+map to the same value in a dictionary.
+
+.. doctest::
+
+   >>> from zope.interface import Interface
+   >>> class I1(Interface): pass
+   >>> orig_I1 = I1
+   >>> class I1(Interface): pass
+   >>> I1 is orig_I1
+   False
+   >>> I1 == orig_I1
+   True
+   >>> d = {I1: 42}
+   >>> dorig_I1
+   42
+   >>> def make_nested():
+   ...     class I1(Interface): pass
+   ...     return I1
+   >>> nested_I1 = make_nested()
+   >>> I1 == orig_I1 == nested_I1
+   True
+
+Caveats
+~~~~~~~
+
+While this behaviour works well with :ref:`pickling (persistence)

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/changes.rst.txt Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/foodforthought.rst.txt Added

@@ -0,0 +1,71 @@
+================================
+Food-based subscription examples
+================================
+
+
+This file gives more subscription examples using a cooking-based example:
+
+.. doctest::
+
+    >>> from zope.interface.adapter import AdapterRegistry
+    >>> registry = AdapterRegistry()
+
+    >>> import zope.interface
+    >>> class IAnimal(zope.interface.Interface):
+    ...     pass
+    >>> class IPoultry(IAnimal):
+    ...     pass
+    >>> class IChicken(IPoultry):
+    ...     pass
+    >>> class ISeafood(IAnimal):
+    ...     pass
+
+Adapting to some other interface for which there is no
+subscription adapter returns an empty sequence:
+
+.. doctest::
+
+    >>> class IRecipe(zope.interface.Interface):
+    ...     pass
+    >>> class ISausages(IRecipe):
+    ...     pass
+    >>> class INoodles(IRecipe):
+    ...     pass
+    >>> class IKFC(IRecipe):
+    ...     pass
+
+    >>> list(registry.subscriptions(IPoultry, IRecipe))
+    
+
+unless we define a subscription:
+
+.. doctest::
+
+    >>> registry.subscribe(IAnimal, ISausages, 'sausages')
+    >>> list(registry.subscriptions(IPoultry, ISausages))
+    'sausages'
+
+And define another subscription adapter:
+
+.. doctest::
+
+    >>> registry.subscribe(IPoultry, INoodles, 'noodles')
+    >>> meals = list(registry.subscriptions(IPoultry, IRecipe))
+    >>> meals.sort()
+    >>> meals
+    'noodles', 'sausages'
+
+    >>> registry.subscribe(IChicken, IKFC, 'kfc')
+    >>> meals = list(registry.subscriptions(IChicken, IRecipe))
+    >>> meals.sort()
+    >>> meals
+    'kfc', 'noodles', 'sausages'
+
+And the answer for poultry hasn't changed:
+
+.. doctest::
+
+    >>> meals = list(registry.subscriptions(IPoultry, IRecipe))
+    >>> meals.sort()
+    >>> meals
+    'noodles', 'sausages'

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/hacking.rst.txt Added

@@ -0,0 +1,312 @@
+Hacking on :mod:`zope.interface`
+================================
+
+
+Getting the Code
+################
+
+The main repository for :mod:`zope.interface` is in the Zope Foundation
+Github repository:
+
+  https://github.com/zopefoundation/zope.interface
+
+You can get a read-only checkout from there:
+
+.. code-block:: sh
+
+   $ git clone https://github.com/zopefoundation/zope.interface.git
+
+or fork it and get a writeable checkout of your fork:
+
+.. code-block:: sh
+
+   $ git clone git@github.com/jrandom/zope.interface.git
+
+The project also mirrors the trunk from the Github repository as a
+Bazaar branch on Launchpad:
+
+https://code.launchpad.net/zope.interface
+
+You can branch the trunk from there using Bazaar:
+
+.. code-block:: sh
+
+   $ bzr branch lp:zope.interface
+
+
+Working in a ``virtualenv``
+###########################
+
+Running the tests
+-----------------
+
+If you use the ``virtualenv`` package to create lightweight Python
+development environments, you can run the tests using nothing more
+than the ``python`` binary in a virtualenv.  First, create a scratch
+environment:
+
+.. code-block:: sh
+
+   $ /path/to/virtualenv --no-site-packages /tmp/hack-zope.interface
+
+Next, get this package registered as a "development egg" in the
+environment:
+
+.. code-block:: sh
+
+   $ /tmp/hack-zope.interface/bin/python setup.py develop
+
+Finally, run the tests using the built-in ``setuptools`` testrunner:
+
+.. code-block:: sh
+
+   $ /tmp/hack-zope.interface/bin/python setup.py test -q
+   running test
+   ...
+   ----------------------------------------------------------------------
+   Ran 2 tests in 0.000s
+
+   OK
+
+The ``dev`` command alias downloads and installs extra tools, like the
+:mod:`nose` testrunner and the :mod:`coverage` coverage analyzer:
+
+.. code-block:: sh
+
+   $ /tmp/hack-zope.interface/bin/python setup.py dev
+   $ /tmp/hack-zope.interface/bin/nosetests
+   running nosetests
+   .................................... (lots more dots)
+   ----------------------------------------------------------------------
+   Ran 707 tests in 2.166s
+
+   OK
+
+If you have the :mod:`coverage` package installed in the virtualenv,
+you can see how well the tests cover the code:
+
+.. code-block:: sh
+
+   $ /tmp/hack-zope.interface/bin/nosetests --with coverage
+   running nosetests
+   .................................... (lots more dots)
+   Name                               Stmts   Miss  Cover   Missing
+   ----------------------------------------------------------------
+   zope.interface                        30      0   100%   
+   zope.interface.adapter               440      0   100%   
+   zope.interface.advice                 69      0   100%   
+   zope.interface.common                  0      0   100%   
+   zope.interface.common.idatetime       98      0   100%   
+   zope.interface.common.interfaces      81      0   100%   
+   zope.interface.common.mapping         32      0   100%   
+   zope.interface.common.sequence        38      0   100%   
+   zope.interface.declarations          312      0   100%   
+   zope.interface.document               54      0   100%   
+   zope.interface.exceptions             21      0   100%   
+   zope.interface.interface             378      0   100%   
+   zope.interface.interfaces            137      0   100%   
+   zope.interface.registry              300      0   100%   
+   zope.interface.ro                     25      0   100%   
+   zope.interface.verify                 48      0   100%   
+   ----------------------------------------------------------------
+   TOTAL                               2063      0   100%   
+   ----------------------------------------------------------------------
+   Ran 707 tests in 2.166s
+
+   OK
+
+
+Building the documentation
+--------------------------
+
+:mod:`zope.interface` uses the nifty :mod:`Sphinx` documentation system
+for building its docs.  Using the same virtualenv you set up to run the
+tests, you can build the docs:
+
+The ``docs`` command alias downloads and installs Sphinx and its dependencies:
+
+.. code-block:: sh
+
+   $ /tmp/hack-zope.interface/bin/python setup.py docs
+   ...
+   $ bin/sphinx-build -b html -d docs/_build/doctrees docs docs/_build/html
+   ...
+   build succeeded.
+
+   Build finished. The HTML pages are in docs/_build/html.
+
+You can also test the code snippets in the documentation:
+
+.. code-block:: sh
+
+   $ bin/sphinx-build -b doctest -d docs/_build/doctrees docs docs/_build/doctest
+   ...
+   running tests...
+
+   Document: index
+   ---------------
+   1 items passed all tests:
+     17 tests in default
+   17 tests in 1 items.
+   17 passed and 0 failed.
+   Test passed.
+
+   Doctest summary
+   ===============
+      17 tests
+       0 failures in tests
+       0 failures in setup code
+   build succeeded.
+   Testing of doctests in the sources finished, look at the  \
+       results in docs/_build/doctest/output.txt.
+
+
+
+Using :mod:`zc.buildout`
+########################
+
+Setting up the buildout
+-----------------------
+
+:mod:`zope.interface` ships with its own :file:`buildout.cfg` file and
+:file:`bootstrap.py` for setting up a development buildout:
+
+.. code-block:: sh
+
+   $ /path/to/python2.7 bootstrap.py
+   ...
+   Generated script '.../bin/buildout'
+   $ bin/buildout
+   Develop: '/home/jrandom/projects/Zope/BTK/interface/.'
+   ...
+   Generated script '.../bin/sphinx-quickstart'.
+   Generated script '.../bin/sphinx-build'.
+
+Running the tests
+-----------------
+
+You can now run the tests:
+
+.. code-block:: sh
+
+   $ bin/test --all
+   Running zope.testing.testrunner.layer.UnitTests tests:
+     Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
+     Ran 702 tests with 0 failures and 0 errors in 0.000 seconds.
+   Tearing down left over layers:
+     Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
+
+

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/human.rst.txt Added

@@ -0,0 +1,180 @@
+==========================
+Using the Adapter Registry
+==========================
+
+This is a small demonstration of the :mod:`zope.interface` package including its
+adapter registry. It is intended to provide a concrete but narrow example on
+how to use interfaces and adapters outside of Zope 3.
+
+First we have to import the interface package:
+
+.. doctest::
+
+  >>> import zope.interface
+
+We now develop an interface for our object, which is a simple file in this
+case. For now we simply support one attribute, the body, which contains the
+actual file contents:
+
+.. doctest::
+
+  >>> class IFile(zope.interface.Interface):
+  ...
+  ...     body = zope.interface.Attribute('Contents of the file.')
+  ...
+
+For statistical reasons we often want to know the size of a file. However, it
+would be clumsy to implement the size directly in the file object, since the
+size really represents meta-data. Thus we create another interface that
+provides the size of something:
+
+.. doctest::
+
+  >>> class ISize(zope.interface.Interface):
+  ...
+  ...     def getSize():
+  ...         'Return the size of an object.'
+  ...
+
+Now we need to implement the file interface. It is essential that the object states
+that it implements the ``IFile`` interface. We also provide a default body
+value (just to make things simpler for this example):
+
+.. doctest::
+
+  >>> @zope.interface.implementer(IFile)
+  ... class File(object):
+  ...
+  ...      body = 'foo bar'
+  ...
+
+Next we implement an adapter that can provide the ``ISize`` interface given any
+object providing ``IFile``. By convention we use ``__used_for__`` to specify the
+interface that we expect the adapted object to provide, in our case
+``IFile``. However, this attribute is not used for anything. If you have
+multiple interfaces for which an adapter is used, just specify the interfaces
+via a tuple.
+
+Again by convention, the constructor of an adapter takes one argument, the
+context. The context in this case is an instance of ``File`` (providing ``IFile``)
+that is used to extract the size from. Also by convention the context is
+stored in an attribute named ``context`` on the adapter. The `twisted`_ community
+refers to the context as the ``original`` object. However, you may feel free to
+use a specific argument name, such as ``file``:
+
+.. doctest::
+
+  >>> @zope.interface.implementer(ISize)
+  ... class FileSize(object):
+  ...
+  ...      __used_for__ = IFile
+  ...
+  ...      def __init__(self, context):
+  ...          self.context = context
+  ...
+  ...      def getSize(self):
+  ...          return len(self.context.body)
+  ...
+
+Now that we have written our adapter, we have to register it with an adapter
+registry, so that it can be looked up when needed. There is no such thing as a
+global registry; thus we have to instantiate one for our example manually:
+
+.. doctest::
+
+  >>> from zope.interface.adapter import AdapterRegistry
+  >>> registry = AdapterRegistry()
+
+
+The registry keeps a map of what adapters implement based on another
+interface the object already provides. Therefore, we next have to register an
+adapter that adapts from ``IFile`` to ``ISize``. The first argument to
+the registry's ``register()`` method is a list of original interfaces.In our
+cause we have only one original interface, ``IFile``. A list makes sense, since
+the interface package has the concept of multi-adapters, which are adapters
+that require multiple objects to adapt to a new interface. In these
+situations, your adapter constructor will require an argument for each
+specified interface.
+
+The second argument is the interface the adapter provides, in our case
+``ISize``. The third argument is the name of the adapter. Since we do not care
+about names, we simply leave it as an empty string. Names are commonly useful,
+if you have adapters for the same set of interfaces, but they are useful in
+different situations. The last argument is simply the adapter class:
+
+.. doctest::
+
+  >>> registry.register(IFile, ISize, '', FileSize)
+
+You can now use the the registry to lookup the adapter:
+
+.. doctest::
+
+  >>> registry.lookup1(IFile, ISize, '')
+  <class 'FileSize'>
+
+Let's get a little bit more practical. Let's create a ``File`` instance and
+create the adapter using a registry lookup. Then we see whether the adapter
+returns the correct size by calling ``getSize()``:
+
+.. doctest::
+
+  >>> file = File()
+  >>> size = registry.lookup1(IFile, ISize, '')(file)
+  >>> size.getSize()
+  7
+
+However, this is not very practical, since I have to manually pass in the
+arguments to the lookup method. There is some syntactic candy that will allow
+us to get an adapter instance by simply calling ``ISize(file)``. To make use of
+this functionality, we need to add our registry to the ``adapter_hooks`` list,
+which is a member of the adapters module. This list stores a collection of
+callables that are automatically invoked when ``IFoo(obj)`` is called; their
+purpose is to locate adapters that implement an interface for a certain
+context instance.
+
+You are required to implement your own adapter hook; this example covers one
+of the simplest hooks that use the registry, but you could implement one that
+used an adapter cache or persistent adapters, for instance. The helper hook is
+required to expect as first argument the desired output interface (for us
+``ISize``) and as the second argument the context of the adapter (here
+``file``). The function returns an adapter, i.e. a ``FileSize`` instance:
+
+.. doctest::
+
+  >>> def hook(provided, object):
+  ...     adapter = registry.lookup1(zope.interface.providedBy(object),
+  ...                                provided, '')
+  ...     return adapter(object)
+  ...
+
+We now just add the hook to an ``adapter_hooks`` list:
+
+.. doctest::
+
+  >>> from zope.interface.interface import adapter_hooks
+  >>> adapter_hooks.append(hook)
+
+Once the hook is registered, you can use the desired syntax:
+
+.. doctest::
+
+  >>> size = ISize(file)
+  >>> size.getSize()
+  7
+
+Now we have to clean up after ourselves, so that others after us have a clean
+``adapter_hooks`` list:
+
+.. doctest::
+
+  >>> adapter_hooks.remove(hook)
+
+That's it. I have intentionally left out a discussion of named adapters and
+multi-adapters, since this text is intended as a practical and simple
+introduction to Zope 3 interfaces and adapters. You might want to read the
+``adapter.txt`` in the ``zope.interface`` package for a more formal, referential
+and complete treatment of the package. Warning: People have reported that
+``adapter.txt`` makes their brain feel soft!
+
+.. _twisted: https://twistedmatrix.com/

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/human.ru.rst.txt Added

@@ -0,0 +1,156 @@
+===============================
+Использование реестра адаптеров
+===============================
+
+Данный документ содержит небольшую демонстрацию пакета ``zope.interface`` и его
+реестра адаптеров. Документ рассчитывался как конкретный, но более узкий пример
+того как использовать интерфейсы и адаптеры вне Zope 3.
+
+Сначала нам необходимо импортировать пакет для работы с интерфейсами::
+
+  >>> import zope.interface
+
+Теперь мы разработаем интерфейс для нашего объекта - простого файла. Наш файл
+будет содержать всего один атрибут - body, в котором фактически будет сохранено
+содержимое файла::
+
+  >>> class IFile(zope.interface.Interface):
+  ...
+  ...     body = zope.interface.Attribute(u'Содержимое файла.')
+  ...
+
+Для статистики нам часто необходимо знать размер файла. Но было бы несколько
+топорно реализовывать определение размера прямо для объекта файла, т.к. размер
+больше относится к мета-данным. Таким образом мы создаем еще один интерфейс для
+представления размера какого-либо объекта::
+
+  >>> class ISize(zope.interface.Interface):
+  ...
+  ...     def getSize():
+  ...         'Return the size of an object.'
+  ...
+
+Теперь мы должны создать класс реализующий наш файл. Необходимо что бы наш
+объект хранил информацию о том, что он реализует интерфейс `IFile`. Мы также
+создаем атрибут с содержимым файла по умолчанию (для упрощения нашего
+примера)::
+
+  >>> class File(object):
+  ...
+  ...      zope.interface.implements(IFile)
+  ...      body = 'foo bar'
+  ...
+
+Дальше мы создаем адаптер, который будет предоставлять интерфейс `ISize`
+получая любой объект предоставляющий интерфейс `IFile`. По соглашению мы
+используем атрибут `__used_for__` для указания интерфейса который как мы
+ожидаем предоставляет адаптируемый объект, `IFile` в нашем случае. На самом
+деле этот атрибут используется только для документирования. В случае если
+адаптер используется для нескольких интерфейсов можно указать их все в виде
+кортежа.
+
+Опять же по соглашению конструктор адаптера получает один аргумент - context
+(контекст). В нашем случае контекст - это экземпляр `IFile` (объект,
+предоставляющий `IFile`) который используется для получения из него размера.
+Так же по соглашению контекст сохраняется а адаптере в атрибуте с именем
+`context`. Twisted комьюнити ссылается на контекст как на объект `original`.
+Таким образом можно также дать аргументу любое подходящее имя, например
+`file`::
+
+  >>> class FileSize(object):
+  ...
+  ...      zope.interface.implements(ISize)
+  ...      __used_for__ = IFile
+  ...
+  ...      def __init__(self, context):
+  ...          self.context = context
+  ...
+  ...      def getSize(self):
+  ...          return len(self.context.body)
+  ...
+
+Теперь когда мы написали наш адаптер мы должны зарегистрировать его в реестре
+адаптеров, что бы его можно было запросить когда он понадобится. Здесь нет
+какого-либо глобального реестра адаптеров, таким образом мы должны
+самостоятельно создать для нашего примера реестр::
+
+  >>> from zope.interface.adapter import AdapterRegistry
+  >>> registry = AdapterRegistry()
+
+Реестр содержит отображение того, что адаптер реализует на основе другого
+интерфейса который предоставляет объект. Поэтому дальше мы регистрируем адаптер
+который адаптирует интерфейс `IFile` к интерфейсу `ISize`. Первый аргумент к
+методу `register()` реестра - это список адаптируемых интерфейсов. В нашем
+случае мы имеем только один адаптируемый интерфейс - `IFile`. Список
+интерфейсов имеет смысл для использования концепции мульти-адаптеров, которые
+требуют нескольких оригинальных объектов для адаптации к новому интерфейсу. В
+этой ситуации конструктор адаптера будет требовать новый аргумент для каждого
+оригинального интерфейса.
+
+Второй аргумент метода `register()` - это интерфейс который предоставляет
+адаптер, в нашем случае `ISize`. Третий аргумент - имя адаптера. Сейчас нам не
+важно имя адаптера и мы передаем его как пустую строку. Обычно имена полезны
+если используются адаптеры для одинакового набора интерфейсов, но в различных
+ситуациях. Последний аргумент - это класс адаптера::
+
+  >>> registry.register(IFile, ISize, '', FileSize)
+
+Теперь мы можем использовать реестр для запроса адаптера::
+
+  >>> registry.lookup1(IFile, ISize, '')
+  <class '__main__.FileSize'>
+
+Попробуем более практичный пример. Создадим экземпляр `File` и создадим адаптер
+использующий запрос реестра. Затем мы увидим возвращает ли адаптер корректный
+размер при вызове `getSize()`::
+
+  >>> file = File()
+  >>> size = registry.lookup1(IFile, ISize, '')(file)
+  >>> size.getSize()
+  7
+
+На самом деле это не очень практично, т.к. нам нужно самим передавать все
+аргументы методу запроса. Существует некоторый синтаксический леденец который
+позволяет нам получить экземпляр адаптера просто вызвав `ISize(file)`. Что бы
+использовать эту функциональность нам понадобится добавить наш реестр к списку
+adapter_hooks, который находится в модуле с адаптерами. Этот список хранит
+коллекцию вызываемых объектов которые вызываются автоматически когда вызывается
+IFoo(obj); их предназначение - найти адаптеры которые реализуют интерфейс для
+определенного экземпляра контекста.
+
+Необходимо реализовать свою собственную функцию для поиска адаптера; данный
+пример описывает одну из простейших функций для использования с реестром, но
+также можно реализовать поисковые функции которые, например, используют
+кэширование, или адаптеры сохраняемые в базе. Функция поиска должна принимать
+желаемый на выходе интерфейс (в нашем случае `ISize`) как первый аргумент и
+контекст для адаптации (`file`) как второй. Функция должна вернуть адаптер,
+т.е. экземпляр `FileSize`::
+
+  >>> def hook(provided, object):
+  ...     adapter = registry.lookup1(zope.interface.providedBy(object),
+  ...                                provided, '')
+  ...     return adapter(object)
+  ...
+
+Теперь мы просто добавляем нашу функцию к списку `adapter_hooks`::
+
+  >>> from zope.interface.interface import adapter_hooks
+  >>> adapter_hooks.append(hook)
+
+Как только функция зарегистрирована мы можем использовать желаемый синтаксис::
+
+  >>> size = ISize(file)
+  >>> size.getSize()
+  7
+
+После нам нужно прибраться за собой, что бы другие получили чистый список
+`adaper_hooks` после нас::
+
+  >>> adapter_hooks.remove(hook)
+
+Это все. Здесь намеренно отложена дискуссия об именованных и мульти-адаптерах,
+т.к. данный текст рассчитан как практическое и простое введение в интерфейсы и
+адаптеры Zope 3. Для более подробной информации имеет смысл прочитать
+`adapter.txt` из пакета `zope.interface`, что бы получить более формальное,
+справочное и полное трактование пакета. Внимание: многие жаловались, что
+`adapter.txt` приводит их мозг к расплавленному состоянию!

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/index.rst.txt Added

_service:tar_scm:zope.interface-5.5.2.tar.gz/docs/_build/html/_sources/verify.rst.txt Added

@@ -0,0 +1,322 @@
+=====================================
+ Verifying interface implementations
+=====================================
+
+The ``zope.interface.verify`` module provides functions that test whether a
+given interface is implemented by a class or provided by an object.
+
+.. currentmodule:: zope.interface.verify
+
+Verifying objects
+=================
+
+.. autofunction:: verifyObject
+
+.. autoexception:: zope.interface.Invalid
+
+Let's demonstrate. We'll begin by defining a simple interface hierarchy
+requiring two attributes, and a helper method that will instantiate and verify
+that an object provides this interface.
+
+.. doctest::
+
+   >>> from zope.interface import Interface, Attribute, implementer
+   >>> from zope.interface import Invalid
+   >>> from zope.interface.verify import verifyObject
+   >>> oname, __name__ = __name__, 'base' # Pretend we're in a module, not a doctest
+   >>> class IBase(Interface):
+   ...     x = Attribute("The X attribute")
+   >>> __name__ = 'module' # Pretend to be a different module.
+   >>> class IFoo(IBase):
+   ...     y = Attribute("The Y attribute")
+   >>> __name__ = oname; del oname
+   >>> class Foo(object):
+   ...     pass
+   >>> def verify_foo(**kwargs):
+   ...    foo = Foo()
+   ...    try:
+   ...        return verifyObject(IFoo, foo, **kwargs)
+   ...    except Invalid as e:
+   ...        print(e)
+
+If we try to verify an instance of this ``Foo`` class, three errors
+will be reported. The declarations (does the object provide ``IFoo``)
+are checked, as are the attributes specified in the interface being
+validated (and its ancestors). Notice that the interface being
+verified is shown, as is the interface where the attribute was
+defined.
+
+.. doctest::
+
+   >>> verify_foo()
+   The object <Foo...> has failed to implement interface ...IFoo:
+       Does not declaratively implement the interface
+       The base.IBase.x attribute was not provided
+       The module.IFoo.y attribute was not provided
+
+If we add the two missing attributes, we still have the error about not
+declaring the correct interface.
+
+.. doctest::
+
+   >>> Foo.x = Foo.y = 42
+   >>> verify_foo()
+   The object <Foo...> has failed to implement interface ...IFoo: Does not declaratively implement the interface.
+
+If we want to only check the structure of the object, without examining
+its declarations, we can use the ``tentative`` argument.
+
+.. doctest::
+
+   >>> verify_foo(tentative=True)
+   True
+
+Of course, we can always mark a particular instance as providing the
+desired interface.
+
+.. doctest::
+
+   >>> from zope.interface import alsoProvides
+   >>> foo = Foo()
+   >>> alsoProvides(foo, IFoo)
+   >>> verifyObject(IFoo, foo)
+   True
+
+If all instances will provide the interface, we can
+mark a class as implementing it. But we have to remove the interface from the
+instance first so a consistent interface resolution order can be achieved.
+(Calling ``gc.collect()`` is also necessary because we use weakrefs.)
+
+.. doctest::
+
+   >>> from zope.interface import classImplements
+   >>> from zope.interface import noLongerProvides
+   >>> import gc
+   >>> noLongerProvides(foo, IFoo)
+   >>> _ = gc.collect()
+   >>> classImplements(Foo, IFoo)
+   >>> verify_foo()
+   True
+
+
+Testing for attributes
+----------------------
+
+Attributes of the object, be they defined by its class or added by its
+``__init__`` method, will be recognized:
+
+.. doctest::
+
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     x = 1
+   ...     def __init__(self):
+   ...         self.y = 2
+
+   >>> verifyObject(IFoo, Foo())
+   True
+
+If either attribute is missing, verification will fail by raising an
+exception.
+
+.. doctest::
+
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     x = 1
+   >>> verify_foo()
+   The object <Foo...> has failed to implement interface ...IFoo: The module.IFoo.y attribute was not provided.
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     def __init__(self):
+   ...         self.y = 2
+   >>> verify_foo()
+   The object <Foo...> has failed to implement interface ...IFoo: The base.IBase.x attribute was not provided.
+
+If both attributes are missing, an exception is raised reporting
+both errors.
+
+.. doctest::
+
+    >>> @implementer(IFoo)
+    ... class Foo(object):
+    ...     pass
+    >>> verify_foo()
+    The object <Foo ...> has failed to implement interface ...IFoo:
+        The base.IBase.x attribute was not provided
+        The module.IFoo.y attribute was not provided
+
+If an attribute is implemented as a property that raises an ``AttributeError``
+when trying to get its value, the attribute is considered missing:
+
+.. doctest::
+
+   >>> oname, __name__ = __name__, 'module'
+   >>> class IFoo(Interface):
+   ...     x = Attribute('The X attribute')
+   >>> __name__ = oname; del oname
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     @property
+   ...     def x(self):
+   ...         raise AttributeError
+   >>> verify_foo()
+   The object <Foo...> has failed to implement interface ...IFoo: The module.IFoo.x attribute was not provided.
+
+
+Any other exception raised by a property will propagate to the caller of
+``verifyObject``:
+
+.. doctest::
+
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     @property
+   ...     def x(self):
+   ...         raise Exception
+   >>> verify_foo()
+   Traceback (most recent call last):
+   Exception
+
+Of course, broken properties that are not required by the interface don't do
+any harm:
+
+.. doctest::
+
+   >>> @implementer(IFoo)
+   ... class Foo(object):
+   ...     x = 1
+   ...     @property
+   ...     def y(self):
+   ...         raise Exception
+   >>> verify_foo()
+   True
+
+
+Testing For Methods
+-------------------
+
+Methods are also validated to exist. We'll start by defining a method

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/adapter.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/docs/adapter.rst Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/api/components.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/docs/api/components.rst Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/api/declarations.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/docs/api/declarations.rst Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/hacking.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/docs/hacking.rst Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/docs/verify.rst -> _service:tar_scm:zope.interface-5.5.2.tar.gz/docs/verify.rst Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/setup.cfg -> _service:tar_scm:zope.interface-5.5.2.tar.gz/setup.cfg Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/setup.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/setup.py Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope.interface.egg-info/PKG-INFO -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope.interface.egg-info/PKG-INFO Changed

@@ -1,1040 +1,12 @@
 Metadata-Version: 2.1
 Name: zope.interface
-Version: 5.4.0
+Version: 5.5.2
 Summary: Interfaces for Python
 Home-page: https://github.com/zopefoundation/zope.interface
 Author: Zope Foundation and Contributors
 Author-email: zope-dev@zope.org
 License: ZPL 2.1
-Description: ====================
-         ``zope.interface``
-        ====================
-        
-        .. image:: https://img.shields.io/pypi/v/zope.interface.svg
-            :target: https://pypi.python.org/pypi/zope.interface/
-            :alt: Latest Version
-        
-        .. image:: https://img.shields.io/pypi/pyversions/zope.interface.svg
-                :target: https://pypi.org/project/zope.interface/
-                :alt: Supported Python versions
-        
-        .. image:: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml/badge.svg
-                :target: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml
-        
-        .. image:: https://readthedocs.org/projects/zopeinterface/badge/?version=latest
-                :target: https://zopeinterface.readthedocs.io/en/latest/
-                :alt: Documentation Status
-        
-        This package is intended to be independently reusable in any Python
-        project. It is maintained by the `Zope Toolkit project
-        <https://zopetoolkit.readthedocs.io/>`_.
-        
-        This package provides an implementation of "object interfaces" for Python.
-        Interfaces are a mechanism for labeling objects as conforming to a given
-        API or contract. So, this package can be considered as implementation of
-        the `Design By Contract`_ methodology support in Python.
-        
-        .. _Design By Contract: http://en.wikipedia.org/wiki/Design_by_contract
-        
-        For detailed documentation, please see https://zopeinterface.readthedocs.io/en/latest/
-        
-        =========
-         Changes
-        =========
-        
-        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 <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>`_.
-        
-        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>`_.
-        
-        5.2.0 (2020-11-05)
-        ==================
-        
-        - Add documentation section ``Persistency and Equality``
-          (`#218 <https://github.com/zopefoundation/zope.interface/issues/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
-          <https://github.com/zopefoundation/zope.interface/pull/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
-          <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
-             ``WeakKey|ValueDictionary``) 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.
-        
-        5.1.0 (2020-04-08)
-        ==================
-        
-        - 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.

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope.interface.egg-info/SOURCES.txt -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope.interface.egg-info/SOURCES.txt Changed

@@ -2,16 +2,19 @@
 .manylinux-install.sh
 .manylinux.sh
 CHANGES.rst
+CONTRIBUTING.md
 COPYRIGHT.txt
 LICENSE.txt
 MANIFEST.in
 README.rst
+appveyor.yml
 build.cmd
 buildout.cfg
 rtd.txt
 setup.cfg
 setup.py
 tox.ini
+benchmarks/micro.py
 docs/Makefile
 docs/README.rst
 docs/README.ru.rst
@@ -26,7 +29,25 @@
 docs/index.rst
 docs/make.bat
 docs/verify.rst
-docs/_static/.gitignore
+docs/_build/doctest/output.txt
+docs/_build/html/_sources/README.rst.txt
+docs/_build/html/_sources/README.ru.rst.txt
+docs/_build/html/_sources/adapter.rst.txt
+docs/_build/html/_sources/adapter.ru.rst.txt
+docs/_build/html/_sources/changes.rst.txt
+docs/_build/html/_sources/foodforthought.rst.txt
+docs/_build/html/_sources/hacking.rst.txt
+docs/_build/html/_sources/human.rst.txt
+docs/_build/html/_sources/human.ru.rst.txt
+docs/_build/html/_sources/index.rst.txt
+docs/_build/html/_sources/verify.rst.txt
+docs/_build/html/_sources/api/adapters.rst.txt
+docs/_build/html/_sources/api/common.rst.txt
+docs/_build/html/_sources/api/components.rst.txt
+docs/_build/html/_sources/api/declarations.rst.txt
+docs/_build/html/_sources/api/index.rst.txt
+docs/_build/html/_sources/api/ro.rst.txt
+docs/_build/html/_sources/api/specifications.rst.txt
 docs/api/adapters.rst
 docs/api/common.rst
 docs/api/components.rst
@@ -81,6 +102,7 @@
 src/zope/interface/tests/odd.py
 src/zope/interface/tests/test_adapter.py
 src/zope/interface/tests/test_advice.py
+src/zope/interface/tests/test_compile_flags.py
 src/zope/interface/tests/test_declarations.py
 src/zope/interface/tests/test_document.py
 src/zope/interface/tests/test_element.py

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/_zope_interface_coptimizations.c -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/_zope_interface_coptimizations.c Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/adapter.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/adapter.py Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/common/tests/__init__.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/common/tests/__init__.py Changed

@@ -60,7 +60,8 @@
 
                 self.assertTrue(self.verify(iface, stdlib_class))
 
-            suffix = "%s_%s_%s" % (
+            suffix = "%s_%s_%s_%s" % (
+                stdlib_class.__module__.replace('.', '_'),
                 stdlib_class.__name__,
                 iface.__module__.replace('.', '_'),
                 iface.__name__
@@ -81,16 +82,17 @@
                 sro = implements.__sro__
                 self.assertIs(sro-1, Interface)
 
-                # Check that we got the strict C3 resolution order, unless we
-                # know we cannot. Note that 'Interface' is virtual base that doesn't
-                # necessarily appear at the same place in the calculated SRO as in the
-                # final SRO.
-                strict = stdlib_class not in self.NON_STRICT_RO
-                isro = ro.ro(implements, strict=strict)
-                isro.remove(Interface)
-                isro.append(Interface)
+                if stdlib_class not in self.UNVERIFIABLE_RO:
+                    # Check that we got the strict C3 resolution order, unless
+                    # we know we cannot. Note that 'Interface' is virtual base
+                    # that doesn't necessarily appear at the same place in the
+                    # calculated SRO as in the final SRO.
+                    strict = stdlib_class not in self.NON_STRICT_RO
+                    isro = ro.ro(implements, strict=strict)
+                    isro.remove(Interface)
+                    isro.append(Interface)
 
-                self.assertEqual(tuple(isro), sro)
+                    self.assertEqual(tuple(isro), sro)
 
             name = 'test_auto_ro_' + suffix
             test_ro.__name__ = name
@@ -101,6 +103,7 @@
     verifier = staticmethod(verifyClass)
     UNVERIFIABLE = ()
     NON_STRICT_RO = ()
+    UNVERIFIABLE_RO = ()
 
     def _adjust_object_before_verify(self, iface, x):
         return x

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/common/tests/test_collections.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/common/tests/test_collections.py Changed

@@ -11,6 +11,7 @@
 ##############################################################################
 
 
+import array
 import unittest
 try:
     import collections.abc as abc
@@ -93,6 +94,10 @@
         # It's imported because...? Coverage imports it, but why do we have it without
         # coverage?
         'Row',
+        # In Python 3.10 ``array.array`` appears as ``IMutableSequence`` but it
+        # does not provide a ``clear()`` method and it cannot be instantiated
+        # using ``array.array()``.
+        array.array,
     }
 
     if PYPY:
@@ -121,6 +126,14 @@
         })
         NON_STRICT_RO = {
         }
+    else:
+        UNVERIFIABLE_RO = {
+            # ``array.array`` fails the ``test_auto_ro_*`` tests with and
+            # without strict RO but only on Windows (AppVeyor) on Python 3.10.0
+            # (in older versions ``array.array`` does not appear as
+            # ``IMutableSequence``).
+            array.array,
+        }
 
 add_abc_interface_tests(TestVerifyClass, collections.ISet.__module__)
 
@@ -158,3 +171,11 @@
         CONSTRUCTORS.update({
             collections.IValuesView: {}.viewvalues,
         })
+    else:
+        UNVERIFIABLE_RO = {
+            # ``array.array`` fails the ``test_auto_ro_*`` tests with and
+            # without strict RO but only on Windows (AppVeyor) on Python 3.10.0
+            # (in older versions ``array.array`` does not appear as
+            # ``IMutableSequence``).
+            array.array,
+        }

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/declarations.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/declarations.py Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/exceptions.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/exceptions.py Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/interfaces.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/interfaces.py Changed

@@ -20,6 +20,7 @@
 from zope.interface.declarations import implementer
 
 __all__ = 
+    'ComponentLookupError',
     'IAdapterRegistration',
     'IAdapterRegistry',
     'IAttribute',
@@ -32,6 +33,7 @@
     'IInterface',
     'IInterfaceDeclaration',
     'IMethod',
+    'Invalid',
     'IObjectEvent',
     'IRegistered',
     'IRegistration',
@@ -40,6 +42,9 @@
     'ISubscriptionAdapterRegistration',
     'IUnregistered',
     'IUtilityRegistration',
+    'ObjectEvent',
+    'Registered',
+    'Unregistered',
 
 
 # pylint:disable=inherit-non-class,no-method-argument,no-self-argument
@@ -1071,7 +1076,7 @@
     """An event related to an object.
 
     The object that generated this event is not necessarily the object
-    refered to by location.
+    referred to by location.
     """
 
     object = Attribute("The subject of the event.")
@@ -1134,7 +1139,7 @@
         """Get subscribers
 
         Subscribers are returned that provide the provided interface
-        and that depend on and are comuted from the sequence of
+        and that depend on and are computed from the sequence of
         required objects.
         """

_service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/tests/test_compile_flags.py Added

@@ -0,0 +1,29 @@
+##############################################################################
+#
+# Copyright (c) 2022 Zope Foundation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE
+#
+##############################################################################
+import struct
+import unittest
+
+import zope.interface  # noqa: try to load a C module for side effects
+
+
+class TestFloatingPoint(unittest.TestCase):
+
+    def test_no_fast_math_optimization(self):
+        # Building with -Ofast enables -ffast-math, which sets certain FPU
+        # flags that can cause breakage elsewhere.  A library such as BTrees
+        # has no business changing global FPU flags for the entire process.
+        zero_bits = struct.unpack("!Q", struct.pack("!d", 0.0))0
+        next_up = zero_bits + 1
+        smallest_subnormal = struct.unpack("!d", struct.pack("!Q", next_up))0
+        self.assertNotEqual(smallest_subnormal, 0.0)

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/tests/test_document.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/tests/test_document.py Changed

@@ -124,7 +124,7 @@
             """ This interface has a method.
             """
             def aMethod():
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -142,7 +142,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -160,7 +160,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second, *rest):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -178,7 +178,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second, **kw):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -221,9 +221,9 @@
 
         class IBase(Interface):
             def method1():
-                pass
+                """docstring"""
             def method2():
-                pass
+                """docstring"""
 
         class IDerived(IBase):
             "IDerived doc"
@@ -233,7 +233,7 @@
             def method3():
                 "method3 doc"
             def method4():
-                pass
+                pass  # pragma: no cover
             def method5():
                 "method5 doc"
 
@@ -348,7 +348,7 @@
             """ This interface has a method.
             """
             def aMethod():
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -366,7 +366,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -384,7 +384,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second, *rest):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -402,7 +402,7 @@
             """ This interface has a method.
             """
             def aMethod(first, second, **kw):
-                pass
+                pass  # pragma: no cover
 
         self.assertEqual(self._callFUT(IHasMethod), EXPECTED)
 
@@ -445,9 +445,9 @@
 
         class IBase(Interface):
             def method1():
-                pass
+                pass  # pragma: no cover
             def method2():
-                pass
+                pass  # pragma: no cover
 
         class IDerived(IBase):
             "IDerived doc"
@@ -457,7 +457,7 @@
             def method3():
                 "method3 doc"
             def method4():
-                pass
+                pass  # pragma: no cover
             def method5():
                 "method5 doc"

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/tests/test_interface.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/tests/test_interface.py Changed

@@ -563,7 +563,7 @@
 
     def test_multiple_inheritance_no_interfaces(self):
         # If we extend an object that implements interfaces,
-        # plus ane that doesn't, we do not interject `Interface`
+        # plus one that doesn't, we do not interject `Interface`
         # early in the resolution order. It stays at the end,
         # like it should.
         # See https://github.com/zopefoundation/zope.interface/issues/8
@@ -1177,9 +1177,9 @@
 
         class ICurrent(Interface):
             def method1(a, b):
-                pass
+                """docstring"""
             def method2(a, b):
-                pass
+                """docstring"""
 
         class IOther(Interface):
             pass
@@ -1207,7 +1207,7 @@
         from zope.interface import providedBy
         class IBase(Interface):
             def method():
-                pass
+                """docstring"""
         class IDerived(IBase):
             pass
         class Current():
@@ -1230,7 +1230,7 @@
 
         class IBase(Interface):
             def method():
-                pass
+                """docstring"""
 
         class IDerived(IBase):
             pass
@@ -1258,7 +1258,7 @@
 
         class ILeft(Interface):
             def method():
-                pass
+                """docstring"""
 
         class IRight(ILeft):
             pass
@@ -1292,7 +1292,7 @@
         class ILeft(Interface):
 
             def method():
-                pass
+                """docstring"""
 
         class IRight(ILeft):
             pass
@@ -1405,7 +1405,7 @@
             attr = Attribute(u'My attr')
 
             def method():
-                pass
+                """docstring"""
 
         self.assertEqual(sorted(ISimple.names()), 'attr', 'method')
 
@@ -1418,16 +1418,16 @@
             attr = Attribute(u'My attr')
 
             def method():
-                pass
+                """docstring"""
 
         class IDerived(IBase):
             attr2 = Attribute(u'My attr2')
 
             def method():
-                pass
+                """docstring"""
 
             def method2():
-                pass
+                """docstring"""
 
         self.assertEqual(sorted(IDerived.names()),
                          'attr2', 'method', 'method2')
@@ -1753,7 +1753,7 @@
 
         class ITagMe(Interface):
             def method():
-                pass
+                """docstring"""
             method.optional = 1
 
         method = ITagMe'method'

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/tests/test_odd_declarations.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/tests/test_odd_declarations.py Changed

_service:tar_scm:zope.interface-5.4.0.tar.gz/src/zope/interface/tests/test_verify.py -> _service:tar_scm:zope.interface-5.5.2.tar.gz/src/zope/interface/tests/test_verify.py Changed

@@ -69,7 +69,7 @@
 
         class ICurrent(Interface):
             def method():
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -84,7 +84,7 @@
 
         class ICurrent(Interface):
             def method():
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -101,7 +101,7 @@
 
         class IBase(Interface):
             def method():
-                pass
+                """docstring"""
 
         class IDerived(IBase):
             pass
@@ -119,7 +119,7 @@
 
         class IBase(Interface):
             def method():
-                pass
+                """docstring"""
 
         class IDerived(IBase):
             pass
@@ -140,7 +140,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -158,7 +158,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -177,7 +177,7 @@
         class ICurrent(Interface):
 
             def method(*args):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -196,7 +196,7 @@
         class ICurrent(Interface):
 
             def method(**kw):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -215,7 +215,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -233,7 +233,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -250,7 +250,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -268,7 +268,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -286,7 +286,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -303,7 +303,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -321,7 +321,7 @@
         class ICurrent(Interface):
 
             def method(a, *args):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -339,7 +339,7 @@
         class ICurrent(Interface):
 
             def method(a, *args):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -356,7 +356,7 @@
         class ICurrent(Interface):
 
             def method(a, *args):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -373,7 +373,7 @@
         class ICurrent(Interface):
 
             def method(**kwargs):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -391,7 +391,7 @@
         class ICurrent(Interface):
 
             def method(*args):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -411,7 +411,7 @@
         class ICurrent(Interface):
 
             def method(**kwargs):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):
@@ -446,7 +446,7 @@
 
         class ICurrent(Interface):
             def method():
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current:
@@ -519,7 +519,7 @@
         class ICurrent(Interface):
 
             def method(a):
-                pass
+                """docstring"""
 
         @implementer(ICurrent)
         class Current(object):

_service:tar_scm:zope.interface-5.4.0.tar.gz/tox.ini -> _service:tar_scm:zope.interface-5.5.2.tar.gz/tox.ini Changed

@@ -1,69 +1,67 @@
+# Generated from:
+# https://github.com/zopefoundation/meta/tree/master/config/c-code
 tox
+minversion = 3.18
 envlist =
-    py27,py27-pure,
-    py35,py35-pure,
-    py36,
-    py37,
-    py38,py38-cext,
-    py39,
-    pypy,
-    pypy3,
-    coverage,
+    lint
+    py27,py27-pure
+    py35,py35-pure
+    py36,py36-pure
+    py37,py37-pure
+    py38,py38-pure
+    py39,py39-pure
+    py310,py310-pure
+    py311,py311-pure
+    pypy
+    pypy3
     docs
-# NB: if you add new environments, please also add them to depends in
-# testenv:coverage so that parallel runs (tox -p auto) will work correctly
+    coverage
 
 testenv
-# ``usedevelop`` is required otherwise unittest complains that it
-# discovers a file in src/... but imports it from .tox/.../
-# ``skip_install`` also basically works, but that causes the ``extras``
-# not to be installed (though ``deps`` still are), and doesn't
-# rebuild C extensions.
 usedevelop = true
-commands =
-    coverage run -p -m unittest discover -s src
-extras = test
+deps =
 setenv =
+    pure: PURE_PYTHON=1
+    !pure-!pypy-!pypy3: PURE_PYTHON=0
     ZOPE_INTERFACE_STRICT_IRO=1
-
-testenv:py27-pure
-setenv =
-    PURE_PYTHON=1
-
-testenv:py35-pure
-setenv =
-    PURE_PYTHON=1
-
-testenv:py38-cext
-# Require the C extension
-setenv =
-    PURE_PYTHON=0
-
-testenv:py
 commands =
-    python --version
-    {testenvcommands}
+    coverage run -p -m unittest discover -s src {posargs}
+    !py27-!pypy: sphinx-build -b doctest -d {envdir}/.cache/doctrees docs {envdir}/.cache/doctest
+extras =
+    test
+    docs
 
 testenv:coverage
-# The -i/--ignore arg is necessary; we get
-# No source for code: '//.tox/pypy/site-packages/zope/interface/__init__.py'
-# without it.
+basepython = python3
+allowlist_externals =
+    mkdir
+deps =
+    coverage
+setenv =
+    PURE_PYTHON=1
 commands =
+    mkdir -p {toxinidir}/parts/htmlcov
     coverage combine
-    coverage report -i
     coverage html -i
-    coverage xml -i
-depends = py27,py27-pure,py35,py35-pure,py36,py37,py38,py38-cext,py39,pypy,pypy3,docs
+    coverage report -i -m --fail-under=99
+depends = py27,py27-pure,py35,py35-pure,py36,py36-pure,py37,py37-pure,py38,py38-pure,py39,py39-pure,py310,py310-pure,pypy,pypy3,docs
 parallel_show_output = true
 
+testenv:lint
+basepython = python3
+skip_install = true
+commands =
+    check-manifest
+    check-python-versions
+deps =
+    check-manifest
+    check-python-versions >= 0.19.1
+    wheel
+
 testenv:docs
-basepython =
-    python3
+basepython = python3
+skip_install = false
+commands_pre =
 commands =
     sphinx-build -b html -d docs/_build/doctrees docs docs/_build/html
-    coverage run -p -m sphinx -b doctest -d docs/_build/doctrees docs docs/_build/doctest
-deps =
-    Sphinx
-    repoze.sphinx.autointerface
-setenv =
-    ZOPE_INTERFACE_STRICT_IRO=0
+    sphinx-build -b doctest -d docs/_build/doctrees docs docs/_build/doctest

Changes of Revision 2