zope.contentprovider
This package provides a framework to develop componentized Web GUI applications. Instead of describing the content of a page using a single template or static system of templates and METAL macros, content provider objects are dynamically looked up based on the setup/configuration of the application.
Detailed documentation is available at https://zopecontentprovider.readthedocs.io
Changes
7.1 (2026-10-22)
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.1 (2025-07-23)
Drop support for Python 3.8.
Add support for Python 3.13.
6.0 (2024-06-07)
Drop support for Python 3.7.
Add support for Python 3.12.
5.0 (2023-04-14)
Drop support for Python 2.7, 3.4, 3.5, 3.6.
Drop support for deprecated python setup.py test.
Add support for Python 3.8, 3.9, 3.10, 3.11.
4.2.1 (2018-11-08)
Fix deprecation warnings.
4.2 (2018-10-05)
Add support for Python 3.7.
Fixed UpdateNotCalled being an instance rather than an exception class (#4).
Host documentation at https://zopecontentprovider.readthedocs.io
4.1.0 (2017-08-08)
Add support for Python 3.5 and 3.6.
Drop support for Python 2.6 and 3.3.
4.0.0 (2014-12-24)
Add support for PyPy and PyPy3.
Add support for Python 3.4.
Add support for testing on Travis.
4.0.0a1 (2013-02-22)
Add Python 3.3 support.
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.7.2 (2010-05-25)
Fix unit tests broken under Python 2.4 by the switch to the standard library doctest module.
3.7.1 (2010-04-30)
Prefer the standard library’s doctest module to the one from zope.testing.
3.7 (2010-04-27)
Since tales:expressiontype is now in zope.browserpage, update conditional ZCML accordingly so it doesn’t depend on the presence of zope.app.pagetemplate anymore.
3.6.1 (2009-12-23)
Ensure that our configure.zcml can be loaded without requiring further dependencies. It uses a tales:expressiontype directive defined in zope.app.pagetemplate. We keep that dependency optional, as not all consumers of this package use ZCML to configure the expression type.
3.6.0 (2009-12-22)
Update test dependency to use zope.browserpage.
3.5.0 (2009-03-18)
Add very simple, but useful base class for implementing content providers, see zope.contentprovider.provider.ContentProviderBase.
Remove unneeded testing dependencies. We only need zope.testing and zope.app.pagetemplate.
Remove zcml slug and old zpkg-related files.
Add setuptools dependency to setup.py.
Clean up package’s description and documentation a bit. Remove duplicate text in README.
Change mailing list address to zope-dev at zope.org instead of retired one.
Change cheeseshop to pypi in the package url.
3.4.0 (2007-10-02)
Initial release independent of the main Zope tree.
Metadata
Release files for zope.contentprovider 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 | |
|---|---|---|---|---|
| zope_contentprovider-7.1.tar.gz | 23.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_contentprovider-7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.0 kB
Release files / zope_contentprovider-7.1.tar.gz
| Download URL | zope_contentprovider-7.1.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79087fdb8b0250dceac82ea8a056ba716be8d9b88751c8f68807c0f882e9b9cf
|
|
BLAKE2b-256 checksum How to use checksums |
fbdb7af50fe684421344ad1007522ed90c5e2bc733e356af2b290ae73ff96ae6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 23, 2026.
Transparency logRelease files / zope_contentprovider-7.1-py3-none-any.whl
| Download URL | zope_contentprovider-7.1-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20d0728f2765d5e5ff385949da61cb95209267e51a8777fe6403e15a5d086cc8
|
|
BLAKE2b-256 checksum How to use checksums |
b025e729bb82f0f0166049dc03453f4cc3d2515e9834ac85805290718c5095dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 23, 2026.
Transparency logSecurity for zope.contentprovider 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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zope_contentprovider-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 Oct 23, 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.
