This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum, jinty, r.david.murray, vstinner, yselivanov
Date 2015-10-28.15:32:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJe_HgLCPFb9UiMsdzXL6SA8naKdWKMc-9ASy-M9QHJkQ@mail.gmail.com>
In-reply-to <1446023395.03.0.913080829015.issue25489@psf.upfronthosting.co.za>
Content
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.

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).
History
Date User Action Args
2015-10-28 15:32:36gvanrossumsetrecipients: + gvanrossum, vstinner, r.david.murray, yselivanov, jinty
2015-10-28 15:32:36gvanrossumlinkissue25489 messages
2015-10-28 15:32:36gvanrossumcreate