zope.generations
Generations are a way of updating objects in the database when the application schema changes. An application schema is essentially the structure of data, the structure of classes in the case of ZODB or the table descriptions in the case of a relational database.
See https://zopegenerations.readthedocs.io/ for complete documentation.
CHANGES
7.1 (2026-11-10)
Add support for Python 3.15.
Drop support for Python 3.10.
Move package metadata from setup.py to pyproject.toml.
Add support for Python 3.14.
Drop support for Python 3.9.
7.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
6.0 (2025-08-08)
Add support for Python 3.11, 3.12, 3.13.
Drop support for Python 2.7, 3.5, 3.6, 3.7, 3.8.
5.1.0 (2022-02-11)
Drop support for Python 3.4.
Add support for Python 3.8, 3.9 and 3.10.
5.0.0 (2019-09-23)
Add support for transaction managers operating in explicit mode. Schema managers were previously required not to commit transactions in their evolve or install methods, but a loophole was open to allow them to commit “if there were no subsequent operations”. That loophole is now closed, at least in explicit mode. See issue 8.
4.1.0 (2018-10-23)
Add support for Python 3.7.
4.0.0 (2017-07-20)
Dropped support for Python 2.6 and 3.3.
Added support for Python 3.4, 3.5, 3.6, PyPy2 and PyPy3.
4.0.0a1 (2013-02-25)
Added support for Python 3.3.
Replaced deprecated zope.interface.implements usage with equivalent zope.interface.implementer decorator.
Dropped support for Python 2.4 and 2.5.
3.7.1 (2011-12-22)
Removed buildout part which was used during development but does not compile on Windows.
Generation scripts add a transaction note.
3.7.0 (2010-09-18)
Initial release extracted from zope.app.generations.
Generations key (stored in database root) has been changed from zope.app.generations to zope.generations. Migration is done when evolve is run the first time by coping the existing generations data over to the new key. So the old and the new key can be used in parallel.
Metadata
Release files for zope.generations 7.1
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 | Actions |
|---|---|---|---|---|
| zope_generations-7.1.tar.gz | 25.2 kB | With provenance | Details for zope_generations-7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zope_generations-7.1-py3-none-any.whl | Python 3 | none | any | Details for zope_generations-7.1-py3-none-any.whl |
Total release size: 51.6 kB
Release files / zope_generations-7.1.tar.gz
| Download URL | zope_generations-7.1.tar.gz |
|---|---|
| Size | 25.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0461c3a00f06cef4c915b0036054d43f44c8999f15d7027567897b01f887db48
|
|
BLAKE2b-256 checksum How to use checksums |
6e9678f1a21a471a4d7d2504877c0dddb68a09224da8155fe7a9f263d08cbb80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logRelease files / zope_generations-7.1-py3-none-any.whl
| Download URL | zope_generations-7.1-py3-none-any.whl |
|---|---|
| Size | 26.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24c7b61d03e4f69d15395ccef2bd1ce6c3c0853cbaac605b1ba790cec93447ff
|
|
BLAKE2b-256 checksum How to use checksums |
936ea1d29287247540d276f97f47678d97a8bd7a5733747414e39c2174902527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logSecurity for zope.generations 7.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for zope_generations-7.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logA 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.