zope.keyreference
Object references that support stable comparison and hashes.
Documentation can be found at https://zopekeyreference.readthedocs.io
Changes
7.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
6.1 (2025-02-14)
Add support for Python 3.12, 3.13.
Drop support for Python 3.7, 3.8.
6.0 (2023-04-25)
Drop support for Python 2.7, 3.5, 3.6.
Add support for Python 3.11.
Make the tests compatible with zope.testing >= 5.
5.0.0 (2022-03-25)
Remove __cmp__ methods. Since the implementation of the rich comparison methods (__eq__, etc) in 4.0a1, the interpreter won’t call __cmp__, even on Python 2. See issue 10.
Add support for Python 3.8, 3.9, and 3.10.
Drop support for Python 3.4.
4.2.0 (2018-10-26)
Add support for Python 3.5, 3.6, and 3.7.
Drop support for Python 2.6 and 3.3.
4.1.0 (2014-12-27)
Add support for PyPy (PyPy3 blocked on PyPy3-compatible zodbpickle).
Add support for Python 3.4.
4.0.0 (2014-12-20)
Add support for testing on Travis.
4.0.0a2 (2013-02-25)
Ensure that the SimpleKeyReference implementation (used for testing) also implements rich comparison properly.
4.0.0a1 (2013-02-22)
Add support for Python 3.3.
Replace deprecated zope.component.adapts usage with equivalent zope.component.adapter decorator.
Replace deprecated zope.interface.implements usage with equivalent zope.interface.implementer decorator.
Drop support for Python 2.4 and 2.5.
3.6.4 (2011-11-30)
Fix tests broken by removal of zope.testing from test dependencies: avoid the ZODB3 module that needs it.
3.6.3 (2011-11-29)
Prefer the standard libraries doctest module to the one from zope.testing.
3.6.2 (2009-09-15)
Make the tests pass with ZODB3.9, which changed the repr() of the persistent classes.
3.6.1 (2009-02-01)
Load keyreferences, pickled by old zope.app.keyreference even if its not installed anymore (so don’t break if one updates a project that don’t directly depends on zope.app.keyreference).
3.6.0 (2009-01-31)
Rename zope.app.keyreference to zope.keyreference.
Metadata
Release files for zope.keyreference 7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zope_keyreference-7.0.tar.gz | 20.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_keyreference-7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.4 kB
Release files / zope_keyreference-7.0.tar.gz
| Download URL | zope_keyreference-7.0.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dec563a76faf3bfed849366fed7a02403e63bdf70b93d8b7c8a3dfa483372d1f
|
|
BLAKE2b-256 checksum How to use checksums |
c772a4c9ab516d01dcc7fcef081c94c77c127fe958ac31c5f7dd38dd58d2367e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / zope_keyreference-7.0-py3-none-any.whl
| Download URL | zope_keyreference-7.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb8b7dc92a1683deef6709a7980df5d8111446b3d46f5e61ef932b4cd49d13d5
|
|
BLAKE2b-256 checksum How to use checksums |
54cea32f0e14993c829ad975f74970625239873183391f3e2ec0bcbbc4f4dbda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for zope.keyreference 7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
