zope.contentprovider
Content Provider Framework for Zope Templates
Decision gist · record as of 2026-08-14
Yes, if you are building a Zope-based web application and need dynamic, component-driven content composition. The package is stable, actively maintained, and dependency-light within the Zope ecosystem. However, verify that ZPL-2.1 licensing fits your project, and note that this is specialized tooling for Zope applications—not a general-purpose templating library. For non-Zope projects, this is not the right fit.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9 or later.
- Integration typically requires ZCML configuration and understanding of the Zope component architecture.
- Low friction install with a wheel distribution.
License · maintenance · safety
ZPL-2.1 (unclear) — Licensed under ZPL-2.1 (Zope Public License). License treatment is marked unclear in the metadata; developers should verify compatibility with their project's licensing requirements before use.
last release 2025-09-12 (336 days) · last repo commit 2026-02-16 · 3 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 130,999 downloads/mo, #11,616 on PyPI
Alternatives
Verify before relying
pip install zope.contentprovider
from zope.contentprovider.provider import ContentProviderBase
from zope.interface import implementer
@implementer(IContentProvider)
class MyProvider(ContentProviderBase):
def render(self):
return "<div>Content</div>"- Whether ZPL-2.1 license is compatible with common open-source and proprietary licensing models
- Practical learning curve and documentation depth for developers new to Zope component architecture
- Real-world usage patterns and community size beyond download statistics
What it is and what it does
zope.contentprovider is a framework for building web applications where page content is assembled dynamically through a component lookup system rather than static templates. Instead of writing monolithic templates or template hierarchies with METAL macros, you define content provider objects that are registered and discovered at runtime based on your application's configuration. This allows different parts of a page to be independently developed, tested, and swapped without modifying templates.
The package is built on the Zope component architecture and integrates with zope.interface, zope.component, and zope.tales for expression evaluation. It provides a ContentProviderBase class as a simple starting point for implementing providers. The framework is stable and actively maintained, supporting modern Python versions (3.9 through 3.13) and PyPy, with no known security vulnerabilities.
Use it for
- Build modular web pages where different sections (header, sidebar, content area) are independently pluggable content providers.
- Implement theme systems where content providers are swapped based on user preferences or application state without template changes.
- Create reusable page components that can be registered and discovered dynamically across a Zope-based application.
- Develop complex web applications where page layout and content composition are driven by configuration rather than template code.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building a Zope-based web application and need dynamic, component-driven content composition.
The package is stable, actively maintained, and dependency-light within the Zope ecosystem. However, verify that ZPL-2.1 licensing fits your project, and note that this is specialized tooling for Zope applications—not a general-purpose templating library. For non-Zope projects, this is not the right fit.
Install
zope-contentprovider on PyPI
Before you install
Low friction install with a wheel distribution. Active maintenance with recent releases; last commit 2026-02-16. Requires Python 3.9 or later and depends on 8 zope ecosystem packages, all of which are established components.
Requires Python 3.9 or later. Integration typically requires ZCML configuration and understanding of the Zope component architecture.
License in practice
Licensed under ZPL-2.1 (Zope Public License). License treatment is marked unclear in the metadata; developers should verify compatibility with their project's licensing requirements before use.
Quickstart
pip install zope.contentprovider
from zope.contentprovider.provider import ContentProviderBase
from zope.interface import implementer
@implementer(IContentProvider)
class MyProvider(ContentProviderBase):
def render(self):
return "<div>Content</div>"Verify before relying
- Whether ZPL-2.1 license is compatible with common open-source and proprietary licensing models
- Practical learning curve and documentation depth for developers new to Zope component architecture
- Real-world usage patterns and community size beyond download statistics
Package facts
| License | ZPL-2.1 unclear |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 8 packagessetuptoolszope.componentzope.eventzope.interfacezope.locationzope.publisherzope.schemazope.tales |
| Maintenance | Actively maintained 336 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 130,999 / month, #11,616 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableEnvironment :: Web EnvironmentFramework :: Zope :: 3Intended Audience :: DevelopersLicense :: OSI Approved :: Zope Public LicenseNatural Language :: EnglishOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.9Programming Language :: Python :: Implementation :: CPythonProgramming Language :: Python :: Implementation :: PyPyTopic :: Internet :: WWW/HTTP |
Evidence: zope_contentprovider-7.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “dynamic content provider framework”
- zope.contentproviderProvides a framework for building componentized web GUI applications…
- zope.viewletzope.viewlet provides a pluggable framework for building modular web…
- AuthlibAuthlib provides a complete implementation of OAuth 1.0, OAuth 2.0,…
Give your agent the search over MCP, or paste the wish link into any chat.
More WWW/HTTP packages
urllib3 is an HTTP client library that provides thread-safe connection pooling, SSL/TLS verification, multipart file uploads, request retries, compression support, and proxy handling for Python applications.
Requests is a Python HTTP library that simplifies sending HTTP/1.1 requests with automatic handling of headers, authentication, cookies, and response parsing.
h11 is a pure-Python HTTP/1.1 protocol implementation that handles parsing and serializing HTTP messages without any built-in I/O, letting you integrate it with any network layer you choose.
HTTPX is a fully featured HTTP client library for Python that provides both sync and async APIs, with support for HTTP/1.1 and HTTP/2, plus an integrated command-line client.
Install it if you are building new projects or modernizing existing ones that rely on HTTP.
A minimal low-level HTTP client library that sends HTTP requests with thread-safe and task-safe connection pooling, supporting HTTP/1.1, HTTP/2, proxies, and both sync and async interfaces.
aiohttp is an async HTTP client and server framework built on asyncio, supporting both WebSockets and middleware-based routing for building concurrent web applications.
Install it if you need async HTTP client or server capabilities in asyncio-based applications.
See also zope.viewlet · zope.browserpage · zope.pagetemplate · zope.browsermenu · zope.browserresource · zope.configuration · z3c.pt · zope.ptresource · zope.contenttype · DocumentTemplate