zope.event README
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 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 doc/index.rst for the documentation.
zope.event Changelog
4.0.0 (2012-05-16)
Automated build of Sphinx HTML docs and running doctest snippets via tox.
Dropped explicit support for Python 2.4 / 2.5 / 3.1.
Added 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.
Added support for continuous integration using tox and jenkins.
Added ‘setup.py dev’ alias (runs setup.py develop plus installs nose and coverage).
Added ‘setup.py docs’ alias (installs Sphinx and dependencies).
3.5.1 (2011-08-04)
Added Sphinx documentation.
3.5.0 (2010-05-01)
Added change log to long-description.
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 4.0.0
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.event-4.0.0.tar.gz | 13.5 kB | Without provenance | Details for zope.event-4.0.0.tar.gz |
Release files / zope.event-4.0.0.tar.gz
| Download URL | zope.event-4.0.0.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2184304e9138d3cc344000feb02fffc7f60f821dee1137581b4f64dae78d510
|
|
BLAKE2b-256 checksum How to use checksums |
4742bbca57104cfb685f60b964147488d2b9945b89a1e9041b5768331de4e8dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.event 4.0.0
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.
