python-zope.interface
This package is intended to be independently reusable in any Python project. It is maintained by the Zope Toolkit project.
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.
- Devel package for openSUSE:Factory
-
11
derived packages
- Links to openSUSE:Factory / python-zope.interface
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:python/python-zope.interface && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _link | 0000000156 156 Bytes | |
| python-zope.interface.changes | 0000008500 8.3 KB | |
| python-zope.interface.spec | 0000003087 3.01 KB | |
| zope.interface-4.3.1.tar.gz | 0000147262 144 KB |
Revision 27 (latest revision is 76)
Dirk Mueller (dirkmueller)
committed
(revision 27)
- update to 4.3.1: - Support Components subclasses that are not hashable. (https://github.com/zopefoundation/zope.interface/issues/53) - Add the ability to sort the objects returned by ``implementedBy``. This is compatible with the way interface classes sort so they can be used together in ordered containers like BTrees. (https://github.com/zopefoundation/zope.interface/issues/42) - Make ``setuptools`` a hard dependency of ``setup.py``. - Change a linear algorithm (O(n)) in ``Components.registerUtility`` and ``Components.unregisterUtility`` into a dictionary lookup (O(1)) for hashable components. This substantially improves the time taken to manipulate utilities in large registries at the cost of some additional memory usage. (https://github.com/zopefoundation/zope.interface/issues/46)
Comments 0