Zope is an open-source web application server.
This document provides some general information about Zope and provides links to other documents. The full documentation can be found at https://zope.readthedocs.io.
Installation
Please visit the installation documentation at https://zope.readthedocs.io/en/latest/INSTALL.html for detailed installation guidance.
License
Zope is licensed under the OSI-approved Zope Public License (ZPL), version 2.1. The full license text is included in LICENSE.txt.
Bug tracker
Bugs reports should be made through the Zope bugtracker at https://github.com/zopefoundation/Zope/issues. A bug report should contain detailed information about how to reproduce the bug.
Change log
These are all changes for Zope 6.
The change log for Zope 4 is at https://github.com/zopefoundation/Zope/blob/4.x/CHANGES.rst. The change log for Zope 5 is at https://github.com/zopefoundation/Zope/blob/5.x/CHANGES.rst.
6.2 (2026-08-05)
Disable XML-RPC request support by default. The protocol is rarely used and disabling it reduces the potential for abuse. Set enable-xmlrpc to on in the Zope configuration if you really need XML-RPC support.
Update to newest compatible versions of dependencies.
Switch to Trusted Publishing for publishing packages to PyPI.
6.1 (2026-04-22)
Update to newest compatible versions of dependencies.
Use ZODB new class_factory parameter to fix registration of ZODB class factory sometimes not beeing effective. See ZODB issue #420.
6.0 (2026-03-04)
Fix bad calls to str in ZMI DTML templates to prevent name shadowing. (#1285)
Update to newest compatible versions of dependencies.
6.0b2 (2026-01-15)
Update to newest compatible versions of dependencies.
Fix installation of console scripts.
6.0b1 (2025-11-22)
Replace pkg_resources namespaces with PEP 420 native namespaces. This change requires using zc.buildout version 5.
Drop support for Python 3.9.
Switch from z3c.checkversions to plone.versioncheck to detect outdated dependency pins as z3c.checkversions no longer works and seems abandoned. See https://github.com/zopefoundation/z3c.checkversions/issues/32
Update to newest compatible versions of dependencies.
Enable multipart/form-data and application/x-www-form-urlencoded support for PATCH requests.
Release files for Zope 6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zope-6.2.tar.gz | 8.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope-6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.3 MB
Release files / zope-6.2.tar.gz
| Download URL | zope-6.2.tar.gz |
|---|---|
| Size | 8.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37b39d696c344c6b5def08127ac2f1c58e8ab2b1c80e412b43bdad437b693c07
|
|
BLAKE2b-256 checksum How to use checksums |
25079faaec50fa4b5f37593c8bbb38bcf85953c1119a1796248557490508aeb7
|
| 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 Aug 5, 2026.
Transparency logRelease files / zope-6.2-py3-none-any.whl
| Download URL | zope-6.2-py3-none-any.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49b95a3baf9c487b73879eeef560b60d10cfc4dcf0705eb0239e23da38412c84
|
|
BLAKE2b-256 checksum How to use checksums |
e60ca5f590aaccf4a881819292de31a2fdd23124cdcbd789b973eebb13329a3f
|
| 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 Aug 5, 2026.
Transparency log
