Brian Sutherland added the comment:
On Wed, Oct 28, 2015 at 03:32:36PM +0000, Guido van Rossum wrote:
>
> Guido van Rossum added the comment:
>
> How about we extend loop.stop() so that you can pass it an exception to
> raise once the loop is stopped? This exception would then be thrown out of
> run_forever(). There may be some delay (callbacks already scheduled will
> run first) but it is how things were meant to be.
It is better than the current situation where to call loop.stop() and
have the correct exit code I would need to resort to a global variable.
I would then probably try to write an exception handler like this:
def exception_handler(loop, context):
loop.stop(context.get('exception', Exception('unknown error')))
And then hope I don't lose the traceback!
> FWIW this isn't really enough to ensure cleanup happens before destructors
> run -- when the loop exits, tasks may still be active unless you keep track
> of all of them and explicitly cancel them (and run the loop until they have
> processed the cancellation).
At least in my situation I don't think this is a problem, the objective
is to shut down the process quickly to prevent bad things happening.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25489>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
