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 vstinner
Recipients gvanrossum, vstinner, yselivanov
Date 2014-11-23.09:32:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1416735123.89.0.671272792173.issue22922@psf.upfronthosting.co.za>
In-reply-to
Content
call_soon() call be called before the event loop starts and after run_forever(), the call will be executed by the next call to run_forever() (or run_until_complete).

But calling call_soon() after close() does not make sense and the user may be surprised to not see its function called. It can be obvious in a simple program, but not in a large application.
History
Date User Action Args
2014-11-23 09:32:03vstinnersetrecipients: + vstinner, gvanrossum, yselivanov
2014-11-23 09:32:03vstinnersetmessageid: <1416735123.89.0.671272792173.issue22922@psf.upfronthosting.co.za>
2014-11-23 09:32:03vstinnerlinkissue22922 messages
2014-11-23 09:32:03vstinnercreate