trio

What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since

What was wrong?

A common BroadcastConfig to use is BroadcastConfig(require_subscriber=False). It would be nice to have a constant for that so applications that are using the event bus can import it directly from lahja.

How can it be fixed?

1. Create a new constant FIRE_AND_FORGET_BROADCASTING in lahja/constants.py

2. Import it in lahja/__init__.py so that it gets r

I totally forgot we have machinery for this in the "muti program" tests. We can likely reuse this on the "external ctrl-c" tests as well!

It doesn't make sense to have the copy-pasted verbose logging configuration in main.py, main_pingpong.py and main_pingpong_servicer.py, which has the effect equal to

logging.basicConfig(format="[%(asctime)s - %(name)s - %(levelname)s]:  %(message)s", level=logging.WARNING)