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 Andrew Lytvyn
Recipients Andrew Lytvyn, asvetlov, gvanrossum, kwarunek, yselivanov
Date 2017-09-22.12:18:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506082720.84.0.408567011767.issue31452@psf.upfronthosting.co.za>
In-reply-to
Content
Guido, look. The point is that if you change run_forever with run_until_complete, then behavior changes: success_coro(5) will not be executed.

I think that it's strange that behavior differs depending on entrypoint: run_forever or run_untill_complete
History
Date User Action Args
2017-09-22 12:18:40Andrew Lytvynsetrecipients: + Andrew Lytvyn, gvanrossum, asvetlov, yselivanov, kwarunek
2017-09-22 12:18:40Andrew Lytvynsetmessageid: <1506082720.84.0.408567011767.issue31452@psf.upfronthosting.co.za>
2017-09-22 12:18:40Andrew Lytvynlinkissue31452 messages
2017-09-22 12:18:40Andrew Lytvyncreate