Message231788
If anybody cares, here is a small patch to implement this. I ran the test suite and nothing else fails because of this change.
However I wonder if this is a slippery slope to go: If call_soon raises after the event loop is closed than everything else that registers an action with the loop should raise as well.
So for consistency this patch should grow quite a bit (unless create_connection, add_reader etc. already raise in this case).
If the decision is to go this path I would also suggest to add a new exception type for "Event loop is closed" so that it can be caught in client code.
YMMV |
|
Date |
User |
Action |
Args |
2014-11-27 23:01:18 | torsten | set | recipients:
+ torsten, gvanrossum, vstinner, yselivanov |
2014-11-27 23:01:18 | torsten | set | messageid: <1417129278.29.0.87686564756.issue22922@psf.upfronthosting.co.za> |
2014-11-27 23:01:18 | torsten | link | issue22922 messages |
2014-11-27 23:01:18 | torsten | create | |
|