zope.event
The zope.event package provides a simple event system, including:
An event publishing API, intended for use by applications which are unaware of any subscribers to their events.
A very simple synchronous event-dispatching system, on which more sophisticated event dispatching systems can be built. For example, a type-based event dispatching system that builds on zope.event can be found in zope.component.
Please see http://zopeevent.readthedocs.io/ for the documentation.
zope.event Changelog
6.2 (2026-04-28)
Move package metadata from setup.py to pyproject.toml.
Allow setuptools < 82 as build system.
6.1 (2025-11-07)
Add support for Python 3.14.
Drop support for Python 3.9.
Remove no longer necessary setuptools runtime dependency.
6.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
5.1.1 (2025-07-22)
Require setuptools >= 75.8.2 to prevent problems with the new packaging standard. (#30)
5.1 (2025-06-26)
Add support for Python 3.12 and 3.13.
Drop support for Python 3.7 and 3.8.
5.0 (2023-06-23)
Drop support for Python 2.7, 3.5, 3.6.
4.6 (2022-12-15)
Port documentation to Python 3.
Add support for Python 3.10, 3.11.
4.5.0 (2020-09-18)
Add support for Python 3.8 and 3.9.
Remove support for Python 3.4.
4.4 (2018-10-05)
Add support for Python 3.7
4.3.0 (2017-07-25)
Add support for Python 3.6.
Drop support for Python 3.3.
4.2.0 (2016-02-17)
Add support for Python 3.5.
Drop support for Python 2.6 and 3.2.
4.1.0 (2015-10-18)
Require 100% branch (as well as statement) coverage.
Add a simple class-based handler implementation.
4.0.3 (2014-03-19)
Add support for Python 3.4.
Update boostrap.py to version 2.2.
4.0.2 (2012-12-31)
Flesh out PyPI Trove classifiers.
Add support for jython 2.7.
4.0.1 (2012-11-21)
Add support for Python 3.3.
4.0.0 (2012-05-16)
Automate build of Sphinx HTML docs and running doctest snippets via tox.
Drop explicit support for Python 2.4 / 2.5 / 3.1.
Add support for PyPy.
3.5.2 (2012-03-30)
This release is the last which will maintain support for Python 2.4 / Python 2.5.
Add support for continuous integration using tox and jenkins.
Add ‘setup.py dev’ alias (runs setup.py develop plus installs nose and coverage).
Add ‘setup.py docs’ alias (installs Sphinx and dependencies).
3.5.1 (2011-08-04)
Add Sphinx documentation.
3.5.0 (2010-05-01)
Add change log to long-description.
Add support for Python 3.x.
3.4.1 (2009-03-03)
A few minor cleanups.
3.4.0 (2007-07-14)
Initial release as a separate project.
Metadata
Release files for zope.event 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 | Provenance | |
|---|---|---|---|---|
| zope_event-6.2.tar.gz | 19.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_event-6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.5 kB
Release files / zope_event-6.2.tar.gz
| Download URL | zope_event-6.2.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b97d5d6327067ee6b9dfcbdf606ade9ade70991e19c162e808ea39e5fcf0f8d3
|
|
BLAKE2b-256 checksum How to use checksums |
9341faa10af34d48d9cd6fa0249a1162943ad84a9590bd1a06939981e6640416
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / zope_event-6.2-py3-none-any.whl
| Download URL | zope_event-6.2-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e755153ac4faf64c10a4b6dd3307680166a3edf65b38df22df592610f8fa874
|
|
BLAKE2b-256 checksum How to use checksums |
9e33848922889e946d4befc415c219fe516af75c49555d8e736e183bfd30db42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for zope.event 6.2
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.
