jpayne@69: Metadata-Version: 2.1
jpayne@69: Name: zope.interface
jpayne@69: Version: 7.2
jpayne@69: Summary: Interfaces for Python
jpayne@69: Home-page: https://github.com/zopefoundation/zope.interface
jpayne@69: Author: Zope Foundation and Contributors
jpayne@69: Author-email: zope-dev@zope.dev
jpayne@69: License: ZPL 2.1
jpayne@69: Keywords: interface,components,plugins
jpayne@69: Classifier: Development Status :: 5 - Production/Stable
jpayne@69: Classifier: Intended Audience :: Developers
jpayne@69: Classifier: License :: OSI Approved :: Zope Public License
jpayne@69: Classifier: Operating System :: OS Independent
jpayne@69: Classifier: Programming Language :: Python
jpayne@69: Classifier: Programming Language :: Python :: 3
jpayne@69: Classifier: Programming Language :: Python :: 3.8
jpayne@69: Classifier: Programming Language :: Python :: 3.9
jpayne@69: Classifier: Programming Language :: Python :: 3.10
jpayne@69: Classifier: Programming Language :: Python :: 3.11
jpayne@69: Classifier: Programming Language :: Python :: 3.12
jpayne@69: Classifier: Programming Language :: Python :: 3.13
jpayne@69: Classifier: Programming Language :: Python :: Implementation :: CPython
jpayne@69: Classifier: Programming Language :: Python :: Implementation :: PyPy
jpayne@69: Classifier: Framework :: Zope :: 3
jpayne@69: Classifier: Topic :: Software Development :: Libraries :: Python Modules
jpayne@69: Requires-Python: >=3.8
jpayne@69: Description-Content-Type: text/x-rst
jpayne@69: License-File: LICENSE.txt
jpayne@69: Requires-Dist: setuptools
jpayne@69: Provides-Extra: docs
jpayne@69: Requires-Dist: Sphinx ; extra == 'docs'
jpayne@69: Requires-Dist: repoze.sphinx.autointerface ; extra == 'docs'
jpayne@69: Requires-Dist: furo ; extra == 'docs'
jpayne@69: Provides-Extra: test
jpayne@69: Requires-Dist: coverage[toml] ; extra == 'test'
jpayne@69: Requires-Dist: zope.event ; extra == 'test'
jpayne@69: Requires-Dist: zope.testing ; extra == 'test'
jpayne@69: Provides-Extra: testing
jpayne@69: Requires-Dist: coverage[toml] ; extra == 'testing'
jpayne@69: Requires-Dist: zope.event ; extra == 'testing'
jpayne@69: Requires-Dist: zope.testing ; extra == 'testing'
jpayne@69:
jpayne@69: ====================
jpayne@69: ``zope.interface``
jpayne@69: ====================
jpayne@69:
jpayne@69: .. image:: https://img.shields.io/pypi/v/zope.interface.svg
jpayne@69: :target: https://pypi.python.org/pypi/zope.interface/
jpayne@69: :alt: Latest Version
jpayne@69:
jpayne@69: .. image:: https://img.shields.io/pypi/pyversions/zope.interface.svg
jpayne@69: :target: https://pypi.org/project/zope.interface/
jpayne@69: :alt: Supported Python versions
jpayne@69:
jpayne@69: .. image:: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml/badge.svg
jpayne@69: :target: https://github.com/zopefoundation/zope.interface/actions/workflows/tests.yml
jpayne@69:
jpayne@69: .. image:: https://readthedocs.org/projects/zopeinterface/badge/?version=latest
jpayne@69: :target: https://zopeinterface.readthedocs.io/en/latest/
jpayne@69: :alt: Documentation Status
jpayne@69:
jpayne@69: This package is intended to be independently reusable in any Python
jpayne@69: project. It is maintained by the `Zope Toolkit project
jpayne@69: `_.
jpayne@69:
jpayne@69: This package provides an implementation of "object interfaces" for Python.
jpayne@69: Interfaces are a mechanism for labeling objects as conforming to a given
jpayne@69: API or contract. So, this package can be considered as implementation of
jpayne@69: the `Design By Contract`_ methodology support in Python.
jpayne@69:
jpayne@69: .. _Design By Contract: http://en.wikipedia.org/wiki/Design_by_contract
jpayne@69:
jpayne@69: For detailed documentation, please see https://zopeinterface.readthedocs.io/en/latest/
jpayne@69:
jpayne@69: =========
jpayne@69: Changes
jpayne@69: =========
jpayne@69:
jpayne@69: 7.2 (2024-11-28)
jpayne@69: ================
jpayne@69:
jpayne@69: - Add preliminary support for Python 3.14a2, this means that
jpayne@69: ``.common.builtins.IByteString`` and ``.common.collections.IByteString`` are
jpayne@69: no longer available from this Python version onwards as Python 3.14 dropped
jpayne@69: ``collections.abc.ByteString``.
jpayne@69:
jpayne@69:
jpayne@69: 7.1.1 (2024-10-23)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix segmentation faults in `weakrefobject.c` on Python 3.12 and 3.13.
jpayne@69: (`#323 `_)
jpayne@69:
jpayne@69:
jpayne@69: 7.1.0 (2024-10-10)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Declare support for Python 3.13.
jpayne@69:
jpayne@69: - Fix segmentation faults on Python 3.13.
jpayne@69: (`#323 `_)
jpayne@69:
jpayne@69:
jpayne@69: 7.0.3 (2024-08-27)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix `Assertion 'memb->type == T_PYSSIZET' failed.` for Python < 3.12.
jpayne@69: (`#319 `_)
jpayne@69:
jpayne@69:
jpayne@69: 7.0.2 (2024-08-26)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix reference-counting bug in C module initialization (broken in 7.0).
jpayne@69: (`#316 `_)
jpayne@69:
jpayne@69:
jpayne@69: 7.0.1 (2024-08-06)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix subclassability of ``ObjectSpecificationDescriptor`` (broken in 7.0).
jpayne@69: (`#312 `_)
jpayne@69:
jpayne@69:
jpayne@69: 7.0 (2024-08-06)
jpayne@69: ================
jpayne@69:
jpayne@69: - Enable heap-based types (PEP 384) for Python >= 3.11.
jpayne@69:
jpayne@69: - Adopt multi-phase module initialization (PEP 489).
jpayne@69:
jpayne@69: - Drop support for Python 3.7.
jpayne@69:
jpayne@69:
jpayne@69: 6.4.post2 (2024-05-24)
jpayne@69: ======================
jpayne@69:
jpayne@69: - Publish missing Windows wheels, second attempt.
jpayne@69: (`#295 `_)
jpayne@69:
jpayne@69:
jpayne@69: 6.4.post1 (2024-05-23)
jpayne@69: ======================
jpayne@69:
jpayne@69: - Publish missing Windows wheels.
jpayne@69: (`#295 `_)
jpayne@69:
jpayne@69:
jpayne@69: 6.4.post0 (2024-05-22)
jpayne@69: ======================
jpayne@69:
jpayne@69: - The sdist of version 6.4 was uploaded to PyPI as
jpayne@69: ``zope_interface-6.4.tar.gz`` instead of ``zope.interface-6.4-py2.tar.gz``
jpayne@69: which cannot be installed by ``zc.buildout``. This release is a re-release
jpayne@69: of version 6.4 with the correct sdist name.
jpayne@69: (`#298 `_)
jpayne@69:
jpayne@69:
jpayne@69: 6.4 (2024-05-15)
jpayne@69: ================
jpayne@69:
jpayne@69: - Adjust for incompatible changes in Python 3.13b1.
jpayne@69: (`#292 `_)
jpayne@69:
jpayne@69: - Build windows wheels on GHA.
jpayne@69:
jpayne@69: 6.3 (2024-04-12)
jpayne@69: ================
jpayne@69:
jpayne@69: - Add preliminary support for Python 3.13 as of 3.13a6.
jpayne@69:
jpayne@69:
jpayne@69: 6.2 (2024-02-16)
jpayne@69: ================
jpayne@69:
jpayne@69: - Add preliminary support for Python 3.13 as of 3.13a3.
jpayne@69:
jpayne@69: - Add support to use the pipe (``|``) syntax for ``typing.Union``.
jpayne@69: (`#280 `_)
jpayne@69:
jpayne@69:
jpayne@69: 6.1 (2023-10-05)
jpayne@69: ================
jpayne@69:
jpayne@69: - Build Linux binary wheels for Python 3.12.
jpayne@69:
jpayne@69: - Add support for Python 3.12.
jpayne@69:
jpayne@69: - Fix building of the docs for non-final versions.
jpayne@69:
jpayne@69:
jpayne@69: 6.0 (2023-03-17)
jpayne@69: ================
jpayne@69:
jpayne@69: - Build Linux binary wheels for Python 3.11.
jpayne@69:
jpayne@69: - Drop support for Python 2.7, 3.5, 3.6.
jpayne@69:
jpayne@69: - Fix test deprecation warning on Python 3.11.
jpayne@69:
jpayne@69: - Add preliminary support for Python 3.12 as of 3.12a5.
jpayne@69:
jpayne@69: - Drop:
jpayne@69:
jpayne@69: + `zope.interface.implements`
jpayne@69: + `zope.interface.implementsOnly`
jpayne@69: + `zope.interface.classProvides`
jpayne@69:
jpayne@69:
jpayne@69: 5.5.2 (2022-11-17)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for building arm64 wheels on macOS.
jpayne@69:
jpayne@69:
jpayne@69: 5.5.1 (2022-11-03)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for final Python 3.11 release.
jpayne@69:
jpayne@69:
jpayne@69: 5.5.0 (2022-10-10)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for Python 3.10 and 3.11 (as of 3.11.0rc2).
jpayne@69:
jpayne@69: - Add missing Trove classifier showing support for Python 3.9.
jpayne@69:
jpayne@69: - Add some more entries to ``zope.interface.interfaces.__all__``.
jpayne@69:
jpayne@69: - Disable unsafe math optimizations in C code. See `pull request 262
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 5.4.0 (2021-04-15)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Make the C implementation of the ``__providedBy__`` descriptor stop
jpayne@69: ignoring all errors raised when accessing the instance's
jpayne@69: ``__provides__``. Now it behaves like the Python version and only
jpayne@69: catches ``AttributeError``. The previous behaviour could lead to
jpayne@69: crashing the interpreter in cases of recursion and errors. See
jpayne@69: `issue 239 `_.
jpayne@69:
jpayne@69: - Update the ``repr()`` and ``str()`` of various objects to be shorter
jpayne@69: and more informative. In many cases, the ``repr()`` is now something
jpayne@69: that can be evaluated to produce an equal object. For example, what
jpayne@69: was previously printed as ```` is now
jpayne@69: shown as ``classImplements(list, IMutableSequence, IIterable)``. See
jpayne@69: `issue 236 `_.
jpayne@69:
jpayne@69: - Make ``Declaration.__add__`` (as in ``implementedBy(Cls) +
jpayne@69: ISomething``) try harder to preserve a consistent resolution order
jpayne@69: when the two arguments share overlapping pieces of the interface
jpayne@69: inheritance hierarchy. Previously, the right hand side was always
jpayne@69: put at the end of the resolution order, which could easily produce
jpayne@69: invalid orders. See `issue 193
jpayne@69: `_.
jpayne@69:
jpayne@69: 5.3.0 (2020-03-21)
jpayne@69: ==================
jpayne@69:
jpayne@69: - No changes from 5.3.0a1
jpayne@69:
jpayne@69:
jpayne@69: 5.3.0a1 (2021-03-18)
jpayne@69: ====================
jpayne@69:
jpayne@69: - Improve the repr of ``zope.interface.Provides`` to remove ambiguity
jpayne@69: about what is being provided. This is especially helpful diagnosing
jpayne@69: IRO issues.
jpayne@69:
jpayne@69: - Allow subclasses of ``BaseAdapterRegistry`` (including
jpayne@69: ``AdapterRegistry`` and ``VerifyingAdapterRegistry``) to have
jpayne@69: control over the data structures. This allows persistent
jpayne@69: implementations such as those based on ZODB to choose more scalable
jpayne@69: options (e.g., BTrees instead of dicts). See `issue 224
jpayne@69: `_.
jpayne@69:
jpayne@69: - Fix a reference counting issue in ``BaseAdapterRegistry`` that could
jpayne@69: lead to references to interfaces being kept around even when all
jpayne@69: utilities/adapters/subscribers providing that interface have been
jpayne@69: removed. This is mostly an issue for persistent implementations.
jpayne@69: Note that this only corrects the issue moving forward, it does not
jpayne@69: solve any already corrupted reference counts. See `issue 227
jpayne@69: `_.
jpayne@69:
jpayne@69: - Add the method ``BaseAdapterRegistry.rebuild()``. This can be used
jpayne@69: to fix the reference counting issue mentioned above, as well as to
jpayne@69: update the data structures when custom data types have changed.
jpayne@69:
jpayne@69: - Add the interface method ``IAdapterRegistry.subscribed()`` and
jpayne@69: implementation ``BaseAdapterRegistry.subscribed()`` for querying
jpayne@69: directly registered subscribers. See `issue 230
jpayne@69: `_.
jpayne@69:
jpayne@69: - Add the maintenance method
jpayne@69: ``Components.rebuildUtilityRegistryFromLocalCache()``. Most users
jpayne@69: will not need this, but it can be useful if the ``Components.utilities``
jpayne@69: registry is suspected to be out of sync with the ``Components``
jpayne@69: object itself (this might happen to persistent ``Components``
jpayne@69: implementations in the face of bugs).
jpayne@69:
jpayne@69: - Fix the ``Provides`` and ``ClassProvides`` descriptors to stop
jpayne@69: allowing redundant interfaces (those already implemented by the
jpayne@69: underlying class or meta class) to produce an inconsistent
jpayne@69: resolution order. This is similar to the change in ``@implementer``
jpayne@69: in 5.1.0, and resolves inconsistent resolution orders with
jpayne@69: ``zope.proxy`` and ``zope.location``. See `issue 207
jpayne@69: `_.
jpayne@69:
jpayne@69: 5.2.0 (2020-11-05)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add documentation section ``Persistency and Equality``
jpayne@69: (`#218 `_).
jpayne@69:
jpayne@69: - Create arm64 wheels.
jpayne@69:
jpayne@69: - Add support for Python 3.9.
jpayne@69:
jpayne@69:
jpayne@69: 5.1.2 (2020-10-01)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Make sure to call each invariant only once when validating invariants.
jpayne@69: Previously, invariants could be called multiple times because when an
jpayne@69: invariant is defined in an interface, it's found by in all interfaces
jpayne@69: inheriting from that interface. See `pull request 215
jpayne@69: `_.
jpayne@69:
jpayne@69: 5.1.1 (2020-09-30)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix the method definitions of ``IAdapterRegistry.subscribe``,
jpayne@69: ``subscriptions`` and ``subscribers``. Previously, they all were
jpayne@69: defined to accept a ``name`` keyword argument, but subscribers have
jpayne@69: no names and the implementation of that interface did not accept
jpayne@69: that argument. See `issue 208
jpayne@69: `_.
jpayne@69:
jpayne@69: - Fix a potential reference leak in the C optimizations. Previously,
jpayne@69: applications that dynamically created unique ``Specification``
jpayne@69: objects (e.g., used ``@implementer`` on dynamic classes) could
jpayne@69: notice a growth of small objects over time leading to increased
jpayne@69: garbage collection times. See `issue 216
jpayne@69: `_.
jpayne@69:
jpayne@69: .. caution::
jpayne@69:
jpayne@69: This leak could prevent interfaces used as the bases of
jpayne@69: other interfaces from being garbage collected. Those interfaces
jpayne@69: will now be collected.
jpayne@69:
jpayne@69: One way in which this would manifest was that ``weakref.ref``
jpayne@69: objects (and things built upon them, like
jpayne@69: ``Weak[Key|Value]Dictionary``) would continue to have access to
jpayne@69: the original object even if there were no other visible
jpayne@69: references to Python and the original object *should* have been
jpayne@69: collected. This could be especially problematic for the
jpayne@69: ``WeakKeyDictionary`` when combined with dynamic or local
jpayne@69: (created in the scope of a function) interfaces, since interfaces
jpayne@69: are hashed based just on their name and module name. See the
jpayne@69: linked issue for an example of a resulting ``KeyError``.
jpayne@69:
jpayne@69: Note that such potential errors are not new, they are just once
jpayne@69: again a possibility.
jpayne@69:
jpayne@69: 5.1.0 (2020-04-08)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Make ``@implementer(*iface)`` and ``classImplements(cls, *iface)``
jpayne@69: ignore redundant interfaces. If the class already implements an
jpayne@69: interface through inheritance, it is no longer redeclared
jpayne@69: specifically for *cls*. This solves many instances of inconsistent
jpayne@69: resolution orders, while still allowing the interface to be declared
jpayne@69: for readability and maintenance purposes. See `issue 199
jpayne@69: `_.
jpayne@69:
jpayne@69: - Remove all bare ``except:`` statements. Previously, when accessing
jpayne@69: special attributes such as ``__provides__``, ``__providedBy__``,
jpayne@69: ``__class__`` and ``__conform__``, this package wrapped such access
jpayne@69: in a bare ``except:`` statement, meaning that many errors could pass
jpayne@69: silently; typically this would result in a fallback path being taken
jpayne@69: and sometimes (like with ``providedBy()``) the result would be
jpayne@69: non-sensical. This is especially true when those attributes are
jpayne@69: implemented with descriptors. Now, only ``AttributeError`` is
jpayne@69: caught. This makes errors more obvious.
jpayne@69:
jpayne@69: Obviously, this means that some exceptions will be propagated
jpayne@69: differently than before. In particular, ``RuntimeError`` raised by
jpayne@69: Acquisition in the case of circular containment will now be
jpayne@69: propagated. Previously, when adapting such a broken object, a
jpayne@69: ``TypeError`` would be the common result, but now it will be a more
jpayne@69: informative ``RuntimeError``.
jpayne@69:
jpayne@69: In addition, ZODB errors like ``POSKeyError`` could now be
jpayne@69: propagated where previously they would ignored by this package.
jpayne@69:
jpayne@69: See `issue 200 `_.
jpayne@69:
jpayne@69: - Require that the second argument (*bases*) to ``InterfaceClass`` is
jpayne@69: a tuple. This only matters when directly using ``InterfaceClass`` to
jpayne@69: create new interfaces dynamically. Previously, an individual
jpayne@69: interface was allowed, but did not work correctly. Now it is
jpayne@69: consistent with ``type`` and requires a tuple.
jpayne@69:
jpayne@69: - Let interfaces define custom ``__adapt__`` methods. This implements
jpayne@69: the other side of the :pep:`246` adaptation protocol: objects being
jpayne@69: adapted could already implement ``__conform__`` if they know about
jpayne@69: the interface, and now interfaces can implement ``__adapt__`` if
jpayne@69: they know about particular objects. There is no performance penalty
jpayne@69: for interfaces that do not supply custom ``__adapt__`` methods.
jpayne@69:
jpayne@69: This includes the ability to add new methods, or override existing
jpayne@69: interface methods using the new ``@interfacemethod`` decorator.
jpayne@69:
jpayne@69: See `issue 3 `_.
jpayne@69:
jpayne@69: - Make the internal singleton object returned by APIs like
jpayne@69: ``implementedBy`` and ``directlyProvidedBy`` for objects that
jpayne@69: implement or provide no interfaces more immutable. Previously an
jpayne@69: internal cache could be mutated. See `issue 204
jpayne@69: `_.
jpayne@69:
jpayne@69: 5.0.2 (2020-03-30)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Ensure that objects that implement no interfaces (such as direct
jpayne@69: subclasses of ``object``) still include ``Interface`` itself in
jpayne@69: their ``__iro___`` and ``__sro___``. This fixes adapter registry
jpayne@69: lookups for such objects when the adapter is registered for
jpayne@69: ``Interface``. See `issue 197
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 5.0.1 (2020-03-21)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Ensure the resolution order for ``InterfaceClass`` is consistent.
jpayne@69: See `issue 192 `_.
jpayne@69:
jpayne@69: - Ensure the resolution order for ``collections.OrderedDict`` is
jpayne@69: consistent on CPython 2. (It was already consistent on Python 3 and PyPy).
jpayne@69:
jpayne@69: - Fix the handling of the ``ZOPE_INTERFACE_STRICT_IRO`` environment
jpayne@69: variable. Previously, ``ZOPE_INTERFACE_STRICT_RO`` was read, in
jpayne@69: contrast with the documentation. See `issue 194
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 5.0.0 (2020-03-19)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Make an internal singleton object returned by APIs like
jpayne@69: ``implementedBy`` and ``directlyProvidedBy`` immutable. Previously,
jpayne@69: it was fully mutable and allowed changing its ``__bases___``. That
jpayne@69: could potentially lead to wrong results in pathological corner
jpayne@69: cases. See `issue 158
jpayne@69: `_.
jpayne@69:
jpayne@69: - Support the ``PURE_PYTHON`` environment variable at runtime instead
jpayne@69: of just at wheel build time. A value of 0 forces the C extensions to
jpayne@69: be used (even on PyPy) failing if they aren't present. Any other
jpayne@69: value forces the Python implementation to be used, ignoring the C
jpayne@69: extensions. See `PR 151 `_.
jpayne@69:
jpayne@69: - Cache the result of ``__hash__`` method in ``InterfaceClass`` as a
jpayne@69: speed optimization. The method is called very often (i.e several
jpayne@69: hundred thousand times during Plone 5.2 startup). Because the hash value never
jpayne@69: changes it can be cached. This improves test performance from 0.614s
jpayne@69: down to 0.575s (1.07x faster). In a real world Plone case a reindex
jpayne@69: index came down from 402s to 320s (1.26x faster). See `PR 156
jpayne@69: `_.
jpayne@69:
jpayne@69: - Change the C classes ``SpecificationBase`` and its subclass
jpayne@69: ``ClassProvidesBase`` to store implementation attributes in their structures
jpayne@69: instead of their instance dictionaries. This eliminates the use of
jpayne@69: an undocumented private C API function, and helps make some
jpayne@69: instances require less memory. See `PR 154 `_.
jpayne@69:
jpayne@69: - Reduce memory usage in other ways based on observations of usage
jpayne@69: patterns in Zope (3) and Plone code bases.
jpayne@69:
jpayne@69: - Specifications with no dependents are common (more than 50%) so
jpayne@69: avoid allocating a ``WeakKeyDictionary`` unless we need it.
jpayne@69: - Likewise, tagged values are relatively rare, so don't allocate a
jpayne@69: dictionary to hold them until they are used.
jpayne@69: - Use ``__slots___`` or the C equivalent ``tp_members`` in more
jpayne@69: common places. Note that this removes the ability to set arbitrary
jpayne@69: instance variables on certain objects.
jpayne@69: See `PR 155 `_.
jpayne@69:
jpayne@69: The changes in this release resulted in a 7% memory reduction after
jpayne@69: loading about 6,000 modules that define about 2,200 interfaces.
jpayne@69:
jpayne@69: .. caution::
jpayne@69:
jpayne@69: Details of many private attributes have changed, and external use
jpayne@69: of those private attributes may break. In particular, the
jpayne@69: lifetime and default value of ``_v_attrs`` has changed.
jpayne@69:
jpayne@69: - Remove support for hashing uninitialized interfaces. This could only
jpayne@69: be done by subclassing ``InterfaceClass``. This has generated a
jpayne@69: warning since it was first added in 2011 (3.6.5). Please call the
jpayne@69: ``InterfaceClass`` constructor or otherwise set the appropriate
jpayne@69: fields in your subclass before attempting to hash or sort it. See
jpayne@69: `issue 157 `_.
jpayne@69:
jpayne@69: - Remove unneeded override of the ``__hash__`` method from
jpayne@69: ``zope.interface.declarations.Implements``. Watching a reindex index
jpayne@69: process in ZCatalog with on a Py-Spy after 10k samples the time for
jpayne@69: ``.adapter._lookup`` was reduced from 27.5s to 18.8s (~1.5x faster).
jpayne@69: Overall reindex index time shrunk from 369s to 293s (1.26x faster).
jpayne@69: See `PR 161
jpayne@69: `_.
jpayne@69:
jpayne@69: - Make the Python implementation closer to the C implementation by
jpayne@69: ignoring all exceptions, not just ``AttributeError``, during (parts
jpayne@69: of) interface adaptation. See `issue 163
jpayne@69: `_.
jpayne@69:
jpayne@69: - Micro-optimization in ``.adapter._lookup`` , ``.adapter._lookupAll``
jpayne@69: and ``.adapter._subscriptions``: By loading ``components.get`` into
jpayne@69: a local variable before entering the loop a bytcode "LOAD_FAST 0
jpayne@69: (components)" in the loop can be eliminated. In Plone, while running
jpayne@69: all tests, average speedup of the "owntime" of ``_lookup`` is ~5x.
jpayne@69: See `PR 167
jpayne@69: `_.
jpayne@69:
jpayne@69: - Add ``__all__`` declarations to all modules. This helps tools that
jpayne@69: do auto-completion and documentation and results in less cluttered
jpayne@69: results. Wildcard ("*") are not recommended and may be affected. See
jpayne@69: `issue 153
jpayne@69: `_.
jpayne@69:
jpayne@69: - Fix ``verifyClass`` and ``verifyObject`` for builtin types like
jpayne@69: ``dict`` that have methods taking an optional, unnamed argument with
jpayne@69: no default value like ``dict.pop``. On PyPy3, the verification is
jpayne@69: strict, but on PyPy2 (as on all versions of CPython) those methods
jpayne@69: cannot be verified and are ignored. See `issue 118
jpayne@69: `_.
jpayne@69:
jpayne@69: - Update the common interfaces ``IEnumerableMapping``,
jpayne@69: ``IExtendedReadMapping``, ``IExtendedWriteMapping``,
jpayne@69: ``IReadSequence`` and ``IUniqueMemberWriteSequence`` to no longer
jpayne@69: require methods that were removed from Python 3 on Python 3, such as
jpayne@69: ``__setslice___``. Now, ``dict``, ``list`` and ``tuple`` properly
jpayne@69: verify as ``IFullMapping``, ``ISequence`` and ``IReadSequence,``
jpayne@69: respectively on all versions of Python.
jpayne@69:
jpayne@69: - Add human-readable ``__str___`` and ``__repr___`` to ``Attribute``
jpayne@69: and ``Method``. These contain the name of the defining interface
jpayne@69: and the attribute. For methods, it also includes the signature.
jpayne@69:
jpayne@69: - Change the error strings raised by ``verifyObject`` and
jpayne@69: ``verifyClass``. They now include more human-readable information
jpayne@69: and exclude extraneous lines and spaces. See `issue 170
jpayne@69: `_.
jpayne@69:
jpayne@69: .. caution:: This will break consumers (such as doctests) that
jpayne@69: depended on the exact error messages.
jpayne@69:
jpayne@69: - Make ``verifyObject`` and ``verifyClass`` report all errors, if the
jpayne@69: candidate object has multiple detectable violations. Previously they
jpayne@69: reported only the first error. See `issue
jpayne@69: `_.
jpayne@69:
jpayne@69: Like the above, this will break consumers depending on the exact
jpayne@69: output of error messages if more than one error is present.
jpayne@69:
jpayne@69: - Add ``zope.interface.common.collections``,
jpayne@69: ``zope.interface.common.numbers``, and ``zope.interface.common.io``.
jpayne@69: These modules define interfaces based on the ABCs defined in the
jpayne@69: standard library ``collections.abc``, ``numbers`` and ``io``
jpayne@69: modules, respectively. Importing these modules will make the
jpayne@69: standard library concrete classes that are registered with those
jpayne@69: ABCs declare the appropriate interface. See `issue 138
jpayne@69: `_.
jpayne@69:
jpayne@69: - Add ``zope.interface.common.builtins``. This module defines
jpayne@69: interfaces of common builtin types, such as ``ITextString`` and
jpayne@69: ``IByteString``, ``IDict``, etc. These interfaces extend the
jpayne@69: appropriate interfaces from ``collections`` and ``numbers``, and the
jpayne@69: standard library classes implement them after importing this module.
jpayne@69: This is intended as a replacement for third-party packages like
jpayne@69: `dolmen.builtins `_.
jpayne@69: See `issue 138 `_.
jpayne@69:
jpayne@69: - Make ``providedBy()`` and ``implementedBy()`` respect ``super``
jpayne@69: objects. For instance, if class ``Derived`` implements ``IDerived``
jpayne@69: and extends ``Base`` which in turn implements ``IBase``, then
jpayne@69: ``providedBy(super(Derived, derived))`` will return ``[IBase]``.
jpayne@69: Previously it would have returned ``[IDerived]`` (in general, it
jpayne@69: would previously have returned whatever would have been returned
jpayne@69: without ``super``).
jpayne@69:
jpayne@69: Along with this change, adapter registries will unpack ``super``
jpayne@69: objects into their ``__self___`` before passing it to the factory.
jpayne@69: Together, this means that ``component.getAdapter(super(Derived,
jpayne@69: self), ITarget)`` is now meaningful.
jpayne@69:
jpayne@69: See `issue 11 `_.
jpayne@69:
jpayne@69: - Fix a potential interpreter crash in the low-level adapter
jpayne@69: registry lookup functions. See issue 11.
jpayne@69:
jpayne@69: - Adopt Python's standard `C3 resolution order
jpayne@69: `_ to compute the
jpayne@69: ``__iro__`` and ``__sro__`` of interfaces, with tweaks to support
jpayne@69: additional cases that are common in interfaces but disallowed for
jpayne@69: Python classes. Previously, an ad-hoc ordering that made no
jpayne@69: particular guarantees was used.
jpayne@69:
jpayne@69: This has many beneficial properties, including the fact that base
jpayne@69: interface and base classes tend to appear near the end of the
jpayne@69: resolution order instead of the beginning. The resolution order in
jpayne@69: general should be more predictable and consistent.
jpayne@69:
jpayne@69: .. caution::
jpayne@69: In some cases, especially with complex interface inheritance
jpayne@69: trees or when manually providing or implementing interfaces, the
jpayne@69: resulting IRO may be quite different. This may affect adapter
jpayne@69: lookup.
jpayne@69:
jpayne@69: The C3 order enforces some constraints in order to be able to
jpayne@69: guarantee a sensible ordering. Older versions of zope.interface did
jpayne@69: not impose similar constraints, so it was possible to create
jpayne@69: interfaces and declarations that are inconsistent with the C3
jpayne@69: constraints. In that event, zope.interface will still produce a
jpayne@69: resolution order equal to the old order, but it won't be guaranteed
jpayne@69: to be fully C3 compliant. In the future, strict enforcement of C3
jpayne@69: order may be the default.
jpayne@69:
jpayne@69: A set of environment variables and module constants allows
jpayne@69: controlling several aspects of this new behaviour. It is possible to
jpayne@69: request warnings about inconsistent resolution orders encountered,
jpayne@69: and even to forbid them. Differences between the C3 resolution order
jpayne@69: and the previous order can be logged, and, in extreme cases, the
jpayne@69: previous order can still be used (this ability will be removed in
jpayne@69: the future). For details, see the documentation for
jpayne@69: ``zope.interface.ro``.
jpayne@69:
jpayne@69: - Make inherited tagged values in interfaces respect the resolution
jpayne@69: order (``__iro__``), as method and attribute lookup does. Previously
jpayne@69: tagged values could give inconsistent results. See `issue 190
jpayne@69: `_.
jpayne@69:
jpayne@69: - Add ``getDirectTaggedValue`` (and related methods) to interfaces to
jpayne@69: allow accessing tagged values irrespective of inheritance. See
jpayne@69: `issue 190
jpayne@69: `_.
jpayne@69:
jpayne@69: - Ensure that ``Interface`` is always the last item in the ``__iro__``
jpayne@69: and ``__sro__``. This is usually the case, but if classes that do
jpayne@69: not implement any interfaces are part of a class inheritance
jpayne@69: hierarchy, ``Interface`` could be assigned too high a priority.
jpayne@69: See `issue 8 `_.
jpayne@69:
jpayne@69: - Implement sorting, equality, and hashing in C for ``Interface``
jpayne@69: objects. In micro benchmarks, this makes those operations 40% to 80%
jpayne@69: faster. This translates to a 20% speed up in querying adapters.
jpayne@69:
jpayne@69: Note that this changes certain implementation details. In
jpayne@69: particular, ``InterfaceClass`` now has a non-default metaclass, and
jpayne@69: it is enforced that ``__module__`` in instances of
jpayne@69: ``InterfaceClass`` is read-only.
jpayne@69:
jpayne@69: See `PR 183 `_.
jpayne@69:
jpayne@69:
jpayne@69: 4.7.2 (2020-03-10)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Remove deprecated use of setuptools features. See `issue 30
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 4.7.1 (2019-11-11)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Use Python 3 syntax in the documentation. See `issue 119
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 4.7.0 (2019-11-11)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Drop support for Python 3.4.
jpayne@69:
jpayne@69: - Change ``queryTaggedValue``, ``getTaggedValue``,
jpayne@69: ``getTaggedValueTags`` in interfaces. They now include inherited
jpayne@69: values by following ``__bases__``. See `PR 144
jpayne@69: `_.
jpayne@69:
jpayne@69: .. caution:: This may be a breaking change.
jpayne@69:
jpayne@69: - Add support for Python 3.8.
jpayne@69:
jpayne@69:
jpayne@69: 4.6.0 (2018-10-23)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for Python 3.7
jpayne@69:
jpayne@69: - Fix ``verifyObject`` for class objects with staticmethods on
jpayne@69: Python 3. See `issue 126
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 4.5.0 (2018-04-19)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Drop support for 3.3, avoid accidental dependence breakage via setup.py.
jpayne@69: See `PR 110 `_.
jpayne@69: - Allow registering and unregistering instance methods as listeners.
jpayne@69: See `issue 12 `_
jpayne@69: and `PR 102 `_.
jpayne@69: - Synchronize and simplify zope/__init__.py. See `issue 114
jpayne@69: `_
jpayne@69:
jpayne@69:
jpayne@69: 4.4.3 (2017-09-22)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Avoid exceptions when the ``__annotations__`` attribute is added to
jpayne@69: interface definitions with Python 3.x type hints. See `issue 98
jpayne@69: `_.
jpayne@69: - Fix the possibility of a rare crash in the C extension when
jpayne@69: deallocating items. See `issue 100
jpayne@69: `_.
jpayne@69:
jpayne@69:
jpayne@69: 4.4.2 (2017-06-14)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix a regression storing
jpayne@69: ``zope.component.persistentregistry.PersistentRegistry`` instances.
jpayne@69: See `issue 85 `_.
jpayne@69:
jpayne@69: - Fix a regression that could lead to the utility registration cache
jpayne@69: of ``Components`` getting out of sync. See `issue 93
jpayne@69: `_.
jpayne@69:
jpayne@69: 4.4.1 (2017-05-13)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Simplify the caching of utility-registration data. In addition to
jpayne@69: simplification, avoids spurious test failures when checking for
jpayne@69: leaks in tests with persistent registries. See `pull 84
jpayne@69: `_.
jpayne@69:
jpayne@69: - Raise ``ValueError`` when non-text names are passed to adapter registry
jpayne@69: methods: prevents corruption of lookup caches.
jpayne@69:
jpayne@69: 4.4.0 (2017-04-21)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Avoid a warning from the C compiler.
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/71)
jpayne@69:
jpayne@69: - Add support for Python 3.6.
jpayne@69:
jpayne@69: 4.3.3 (2016-12-13)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Correct typos and ReST formatting errors in documentation.
jpayne@69:
jpayne@69: - Add API documentation for the adapter registry.
jpayne@69:
jpayne@69: - Ensure that the ``LICENSE.txt`` file is included in built wheels.
jpayne@69:
jpayne@69: - Fix C optimizations broken on Py3k. See the Python bug at:
jpayne@69: http://bugs.python.org/issue15657
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/60)
jpayne@69:
jpayne@69:
jpayne@69: 4.3.2 (2016-09-05)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix equality testing of ``implementedBy`` objects and proxies.
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/55)
jpayne@69:
jpayne@69:
jpayne@69: 4.3.1 (2016-08-31)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Support Components subclasses that are not hashable.
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/53)
jpayne@69:
jpayne@69:
jpayne@69: 4.3.0 (2016-08-31)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add the ability to sort the objects returned by ``implementedBy``.
jpayne@69: This is compatible with the way interface classes sort so they can
jpayne@69: be used together in ordered containers like BTrees.
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/42)
jpayne@69:
jpayne@69: - Make ``setuptools`` a hard dependency of ``setup.py``.
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/13)
jpayne@69:
jpayne@69: - Change a linear algorithm (O(n)) in ``Components.registerUtility`` and
jpayne@69: ``Components.unregisterUtility`` into a dictionary lookup (O(1)) for
jpayne@69: hashable components. This substantially improves the time taken to
jpayne@69: manipulate utilities in large registries at the cost of some
jpayne@69: additional memory usage. (https://github.com/zopefoundation/zope.interface/issues/46)
jpayne@69:
jpayne@69:
jpayne@69: 4.2.0 (2016-06-10)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for Python 3.5
jpayne@69:
jpayne@69: - Drop support for Python 2.6 and 3.2.
jpayne@69:
jpayne@69:
jpayne@69: 4.1.3 (2015-10-05)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix installation without a C compiler on Python 3.5
jpayne@69: (https://github.com/zopefoundation/zope.interface/issues/24).
jpayne@69:
jpayne@69:
jpayne@69: 4.1.2 (2014-12-27)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for PyPy3.
jpayne@69:
jpayne@69: - Remove unittest assertions deprecated in Python3.x.
jpayne@69:
jpayne@69: - Add ``zope.interface.document.asReStructuredText``, which formats the
jpayne@69: generated text for an interface using ReST double-backtick markers.
jpayne@69:
jpayne@69:
jpayne@69: 4.1.1 (2014-03-19)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for Python 3.4.
jpayne@69:
jpayne@69:
jpayne@69: 4.1.0 (2014-02-05)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Update ``boostrap.py`` to version 2.2.
jpayne@69:
jpayne@69: - Add ``@named(name)`` declaration, that specifies the component name, so it
jpayne@69: does not have to be passed in during registration.
jpayne@69:
jpayne@69:
jpayne@69: 4.0.5 (2013-02-28)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix a bug where a decorated method caused false positive failures on
jpayne@69: ``verifyClass()``.
jpayne@69:
jpayne@69:
jpayne@69: 4.0.4 (2013-02-21)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix a bug that was revealed by porting zope.traversing. During a loop, the
jpayne@69: loop body modified a weakref dict causing a ``RuntimeError`` error.
jpayne@69:
jpayne@69: 4.0.3 (2012-12-31)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fleshed out PyPI Trove classifiers.
jpayne@69:
jpayne@69: 4.0.2 (2012-11-21)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Add support for Python 3.3.
jpayne@69:
jpayne@69: - Restored ability to install the package in the absence of ``setuptools``.
jpayne@69:
jpayne@69: - LP #1055223: Fix test which depended on dictionary order and failed randomly
jpayne@69: in Python 3.3.
jpayne@69:
jpayne@69: 4.0.1 (2012-05-22)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Drop explicit ``DeprecationWarnings`` for "class advice" APIS (these
jpayne@69: APIs are still deprecated under Python 2.x, and still raise an exception
jpayne@69: under Python 3.x, but no longer cause a warning to be emitted under
jpayne@69: Python 2.x).
jpayne@69:
jpayne@69: 4.0.0 (2012-05-16)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Automated build of Sphinx HTML docs and running doctest snippets via tox.
jpayne@69:
jpayne@69: - Deprecate the "class advice" APIs from ``zope.interface.declarations``:
jpayne@69: ``implements``, ``implementsOnly``, and ``classProvides``. In their place,
jpayne@69: prefer the equivalent class decorators: ``@implementer``,
jpayne@69: ``@implementer_only``, and ``@provider``. Code which uses the deprecated
jpayne@69: APIs will not work as expected under Py3k.
jpayne@69:
jpayne@69: - Remove use of '2to3' and associated fixers when installing under Py3k.
jpayne@69: The code is now in a "compatible subset" which supports Python 2.6, 2.7,
jpayne@69: and 3.2, including PyPy 1.8 (the version compatible with the 2.7 language
jpayne@69: spec).
jpayne@69:
jpayne@69: - Drop explicit support for Python 2.4 / 2.5 / 3.1.
jpayne@69:
jpayne@69: - Add support for PyPy.
jpayne@69:
jpayne@69: - Add support for continuous integration using ``tox`` and ``jenkins``.
jpayne@69:
jpayne@69: - Add 'setup.py dev' alias (runs ``setup.py develop`` plus installs
jpayne@69: ``nose`` and ``coverage``).
jpayne@69:
jpayne@69: - Add 'setup.py docs' alias (installs ``Sphinx`` and dependencies).
jpayne@69:
jpayne@69: - Replace all unittest coverage previously accomplished via doctests with
jpayne@69: unittests. The doctests have been moved into a ``docs`` section, managed
jpayne@69: as a Sphinx collection.
jpayne@69:
jpayne@69: - LP #910987: Ensure that the semantics of the ``lookup`` method of
jpayne@69: ``zope.interface.adapter.LookupBase`` are the same in both the C and
jpayne@69: Python implementations.
jpayne@69:
jpayne@69: - LP #900906: Avoid exceptions due to tne new ``__qualname__`` attribute
jpayne@69: added in Python 3.3 (see PEP 3155 for rationale). Thanks to Antoine
jpayne@69: Pitrou for the patch.
jpayne@69:
jpayne@69: 3.8.0 (2011-09-22)
jpayne@69: ==================
jpayne@69:
jpayne@69: - New module ``zope.interface.registry``. This is code moved from
jpayne@69: ``zope.component.registry`` which implements a basic nonperistent component
jpayne@69: registry as ``zope.interface.registry.Components``. This class was moved
jpayne@69: from ``zope.component`` to make porting systems (such as Pyramid) that rely
jpayne@69: only on a basic component registry to Python 3 possible without needing to
jpayne@69: port the entirety of the ``zope.component`` package. Backwards
jpayne@69: compatibility import shims have been left behind in ``zope.component``, so
jpayne@69: this change will not break any existing code.
jpayne@69:
jpayne@69: - New ``tests_require`` dependency: ``zope.event`` to test events sent by
jpayne@69: Components implementation. The ``zope.interface`` package does not have a
jpayne@69: hard dependency on ``zope.event``, but if ``zope.event`` is importable, it
jpayne@69: will send component registration events when methods of an instance of
jpayne@69: ``zope.interface.registry.Components`` are called.
jpayne@69:
jpayne@69: - New interfaces added to support ``zope.interface.registry.Components``
jpayne@69: addition: ``ComponentLookupError``, ``Invalid``, ``IObjectEvent``,
jpayne@69: ``ObjectEvent``, ``IComponentLookup``, ``IRegistration``,
jpayne@69: ``IUtilityRegistration``, ``IAdapterRegistration``,
jpayne@69: ``ISubscriptionAdapterRegistration``, ``IHandlerRegistration``,
jpayne@69: ``IRegistrationEvent``, ``RegistrationEvent``, ``IRegistered``,
jpayne@69: ``Registered``, ``IUnregistered``, ``Unregistered``,
jpayne@69: ``IComponentRegistry``, and ``IComponents``.
jpayne@69:
jpayne@69: - No longer Python 2.4 compatible (tested under 2.5, 2.6, 2.7, and 3.2).
jpayne@69:
jpayne@69: 3.7.0 (2011-08-13)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Move changes from 3.6.2 - 3.6.5 to a new 3.7.x release line.
jpayne@69:
jpayne@69: 3.6.7 (2011-08-20)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix sporadic failures on x86-64 platforms in tests of rich comparisons
jpayne@69: of interfaces.
jpayne@69:
jpayne@69: 3.6.6 (2011-08-13)
jpayne@69: ==================
jpayne@69:
jpayne@69: - LP #570942: Now correctly compare interfaces from different modules but
jpayne@69: with the same names.
jpayne@69:
jpayne@69: N.B.: This is a less intrusive / destabilizing fix than the one applied in
jpayne@69: 3.6.3: we only fix the underlying cmp-alike function, rather than adding
jpayne@69: the other "rich comparison" functions.
jpayne@69:
jpayne@69: - Revert to software as released with 3.6.1 for "stable" 3.6 release branch.
jpayne@69:
jpayne@69: 3.6.5 (2011-08-11)
jpayne@69: ==================
jpayne@69:
jpayne@69: - LP #811792: work around buggy behavior in some subclasses of
jpayne@69: ``zope.interface.interface.InterfaceClass``, which invoke ``__hash__``
jpayne@69: before initializing ``__module__`` and ``__name__``. The workaround
jpayne@69: returns a fixed constant hash in such cases, and issues a ``UserWarning``.
jpayne@69:
jpayne@69: - LP #804832: Under PyPy, ``zope.interface`` should not build its C
jpayne@69: extension. Also, prevent attempting to build it under Jython.
jpayne@69:
jpayne@69: - Add a tox.ini for easier xplatform testing.
jpayne@69:
jpayne@69: - Fix testing deprecation warnings issued when tested under Py3K.
jpayne@69:
jpayne@69: 3.6.4 (2011-07-04)
jpayne@69: ==================
jpayne@69:
jpayne@69: - LP 804951: InterfaceClass instances were unhashable under Python 3.x.
jpayne@69:
jpayne@69: 3.6.3 (2011-05-26)
jpayne@69: ==================
jpayne@69:
jpayne@69: - LP #570942: Now correctly compare interfaces from different modules but
jpayne@69: with the same names.
jpayne@69:
jpayne@69: 3.6.2 (2011-05-17)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Moved detailed documentation out-of-line from PyPI page, linking instead to
jpayne@69: http://docs.zope.org/zope.interface .
jpayne@69:
jpayne@69: - Fixes for small issues when running tests under Python 3.2 using
jpayne@69: ``zope.testrunner``.
jpayne@69:
jpayne@69: - LP # 675064: Specify return value type for C optimizations module init
jpayne@69: under Python 3: undeclared value caused warnings, and segfaults on some
jpayne@69: 64 bit architectures.
jpayne@69:
jpayne@69: - setup.py now raises RuntimeError if you don't have Distutils installed when
jpayne@69: running under Python 3.
jpayne@69:
jpayne@69: 3.6.1 (2010-05-03)
jpayne@69: ==================
jpayne@69:
jpayne@69: - A non-ASCII character in the changelog made 3.6.0 uninstallable on
jpayne@69: Python 3 systems with another default encoding than UTF-8.
jpayne@69:
jpayne@69: - Fix compiler warnings under GCC 4.3.3.
jpayne@69:
jpayne@69: 3.6.0 (2010-04-29)
jpayne@69: ==================
jpayne@69:
jpayne@69: - LP #185974: Clear the cache used by ``Specificaton.get`` inside
jpayne@69: ``Specification.changed``. Thanks to Jacob Holm for the patch.
jpayne@69:
jpayne@69: - Add support for Python 3.1. Contributors:
jpayne@69:
jpayne@69: Lennart Regebro
jpayne@69: Martin v Loewis
jpayne@69: Thomas Lotze
jpayne@69: Wolfgang Schnerring
jpayne@69:
jpayne@69: The 3.1 support is completely backwards compatible. However, the implements
jpayne@69: syntax used under Python 2.X does not work under 3.X, since it depends on
jpayne@69: how metaclasses are implemented and this has changed. Instead it now supports
jpayne@69: a decorator syntax (also under Python 2.X)::
jpayne@69:
jpayne@69: class Foo:
jpayne@69: implements(IFoo)
jpayne@69: ...
jpayne@69:
jpayne@69: can now also be written::
jpayne@69:
jpayne@69: @implementer(IFoo):
jpayne@69: class Foo:
jpayne@69: ...
jpayne@69:
jpayne@69: There are 2to3 fixers available to do this change automatically in the
jpayne@69: zope.fixers package.
jpayne@69:
jpayne@69: - Python 2.3 is no longer supported.
jpayne@69:
jpayne@69:
jpayne@69: 3.5.4 (2009-12-23)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Use the standard Python doctest module instead of zope.testing.doctest, which
jpayne@69: has been deprecated.
jpayne@69:
jpayne@69:
jpayne@69: 3.5.3 (2009-12-08)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix an edge case: make providedBy() work when a class has '__provides__' in
jpayne@69: its __slots__ (see http://thread.gmane.org/gmane.comp.web.zope.devel/22490)
jpayne@69:
jpayne@69:
jpayne@69: 3.5.2 (2009-07-01)
jpayne@69: ==================
jpayne@69:
jpayne@69: - BaseAdapterRegistry.unregister, unsubscribe: Remove empty portions of
jpayne@69: the data structures when something is removed. This avoids leaving
jpayne@69: references to global objects (interfaces) that may be slated for
jpayne@69: removal from the calling application.
jpayne@69:
jpayne@69:
jpayne@69: 3.5.1 (2009-03-18)
jpayne@69: ==================
jpayne@69:
jpayne@69: - verifyObject: use getattr instead of hasattr to test for object attributes
jpayne@69: in order to let exceptions other than AttributeError raised by properties
jpayne@69: propagate to the caller
jpayne@69:
jpayne@69: - Add Sphinx-based documentation building to the package buildout
jpayne@69: configuration. Use the ``bin/docs`` command after buildout.
jpayne@69:
jpayne@69: - Improve package description a bit. Unify changelog entries formatting.
jpayne@69:
jpayne@69: - Change package's mailing list address to zope-dev at zope.org as
jpayne@69: zope3-dev at zope.org is now retired.
jpayne@69:
jpayne@69:
jpayne@69: 3.5.0 (2008-10-26)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix declaration of _zope_interface_coptimizations, it's not a top level
jpayne@69: package.
jpayne@69:
jpayne@69: - Add a DocTestSuite for odd.py module, so their tests are run.
jpayne@69:
jpayne@69: - Allow to bootstrap on Jython.
jpayne@69:
jpayne@69: - Fix https://bugs.launchpad.net/zope3/3.3/+bug/98388: ISpecification
jpayne@69: was missing a declaration for __iro__.
jpayne@69:
jpayne@69: - Add optional code optimizations support, which allows the building
jpayne@69: of C code optimizations to fail (Jython).
jpayne@69:
jpayne@69: - Replace `_flatten` with a non-recursive implementation, effectively making
jpayne@69: it 3x faster.
jpayne@69:
jpayne@69:
jpayne@69: 3.4.1 (2007-10-02)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Fix a setup bug that prevented installation from source on systems
jpayne@69: without setuptools.
jpayne@69:
jpayne@69:
jpayne@69: 3.4.0 (2007-07-19)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Final release for 3.4.0.
jpayne@69:
jpayne@69:
jpayne@69: 3.4.0b3 (2007-05-22)
jpayne@69: ====================
jpayne@69:
jpayne@69:
jpayne@69: - When checking whether an object is already registered, use identity
jpayne@69: comparison, to allow adding registering with picky custom comparison methods.
jpayne@69:
jpayne@69:
jpayne@69: 3.3.0.1 (2007-01-03)
jpayne@69: ====================
jpayne@69:
jpayne@69: - Made a reference to OverflowWarning, which disappeared in Python
jpayne@69: 2.5, conditional.
jpayne@69:
jpayne@69:
jpayne@69: 3.3.0 (2007/01/03)
jpayne@69: ==================
jpayne@69:
jpayne@69: New Features
jpayne@69: ------------
jpayne@69:
jpayne@69: - Refactor the adapter-lookup algorithim to make it much simpler and faster.
jpayne@69:
jpayne@69: Also, implement more of the adapter-lookup logic in C, making
jpayne@69: debugging of application code easier, since there is less
jpayne@69: infrastructre code to step through.
jpayne@69:
jpayne@69: - Treat objects without interface declarations as if they
jpayne@69: declared that they provide ``zope.interface.Interface``.
jpayne@69:
jpayne@69: - Add a number of richer new adapter-registration interfaces
jpayne@69: that provide greater control and introspection.
jpayne@69:
jpayne@69: - Add a new interface decorator to zope.interface that allows the
jpayne@69: setting of tagged values on an interface at definition time (see
jpayne@69: zope.interface.taggedValue).
jpayne@69:
jpayne@69: Bug Fixes
jpayne@69: ---------
jpayne@69:
jpayne@69: - A bug in multi-adapter lookup sometimes caused incorrect adapters to
jpayne@69: be returned.
jpayne@69:
jpayne@69:
jpayne@69: 3.2.0.2 (2006-04-15)
jpayne@69: ====================
jpayne@69:
jpayne@69: - Fix packaging bug: 'package_dir' must be a *relative* path.
jpayne@69:
jpayne@69:
jpayne@69: 3.2.0.1 (2006-04-14)
jpayne@69: ====================
jpayne@69:
jpayne@69: - Packaging change: suppress inclusion of 'setup.cfg' in 'sdist' builds.
jpayne@69:
jpayne@69:
jpayne@69: 3.2.0 (2006-01-05)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Corresponds to the version of the zope.interface package shipped as part of
jpayne@69: the Zope 3.2.0 release.
jpayne@69:
jpayne@69:
jpayne@69: 3.1.0 (2005-10-03)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Corresponds to the version of the zope.interface package shipped as part of
jpayne@69: the Zope 3.1.0 release.
jpayne@69:
jpayne@69: - Made attribute resolution order consistent with component lookup order,
jpayne@69: i.e. new-style class MRO semantics.
jpayne@69:
jpayne@69: - Deprecate 'isImplementedBy' and 'isImplementedByInstancesOf' APIs in
jpayne@69: favor of 'implementedBy' and 'providedBy'.
jpayne@69:
jpayne@69:
jpayne@69: 3.0.1 (2005-07-27)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Corresponds to the version of the zope.interface package shipped as part of
jpayne@69: the Zope X3.0.1 release.
jpayne@69:
jpayne@69: - Fix a bug reported by James Knight, which caused adapter registries
jpayne@69: to fail occasionally to reflect declaration changes.
jpayne@69:
jpayne@69:
jpayne@69: 3.0.0 (2004-11-07)
jpayne@69: ==================
jpayne@69:
jpayne@69: - Corresponds to the version of the zope.interface package shipped as part of
jpayne@69: the Zope X3.0.0 release.