zopefoundation / zope.event

Event publishing / dispatch, used by Zope Component Architecture

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's Issues

Deprecated setuptools parameter

PROBLEM REPORT

What I did:

I installed this package on gentoo

What I expect to happen:

Just that the package would install without anything specific

What actually happened:

I got a QA warning saying the following:

• Messages for package dev-python/zope-event-5.0:

• Log file: /var/log/portage/build/dev-python/zope-event-5.0:20240503-195705.log

• QA Notice: setuptools warnings detected:

•  The namespace_packages parameter is deprecated.
  

What version of Python and Zope/Addons I am using:

I was on python3.11 and python3.12 on Gentoo and compiling from sources.

LICENSE file missing from latest release

Tools such as pip-licenses use the LICENSE file included in uploaded Python packages to generate license reports. The latest release of zope.event does not have a LICENSE file included.

Could a new release of zope.event be released using the latest wheel library that pulls in the LICENSE file automatically?

4.3 release to PyPI?

This is needed for zopefoundation/zopetoolkit#8

I'd be happy to do so, given access.

Documentation - Sync vs. Async

Hey,
If I'm not mistaken, the basic event system is synchronous (meaning that after dispatch, the process will wait until all subscribers have processed the event). This may be worth mentioning in the README and documentation.

Add support for Python 3.6

And modernize/standardize tox.ini/.travis.yml. (I don't see any reason we can't use coverage and zope.testrunner here too. I mean, there's not much to cover, but still. That wouldn't seem to introduce any circular dependencies.)