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 pitrou
Recipients giampaolo.rodola, gvanrossum, pitrou, vstinner, yselivanov
Date 2017-11-07.15:31:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510068675.83.0.213398074469.issue31960@psf.upfronthosting.co.za>
In-reply-to
Content
> My opinion on this: update documentation for all Python versions to reflect that Future uses call_soon.

Agreed.

> I think we should update `Future._schedule_callbacks` to check if the loop is in debug mode.

Unfortunately this is not sufficient for the snippet I posted.  The loop's thread_id is only set when the loop runs, but the main loop in that example never runs.
History
Date User Action Args
2017-11-07 15:31:15pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, yselivanov
2017-11-07 15:31:15pitrousetmessageid: <1510068675.83.0.213398074469.issue31960@psf.upfronthosting.co.za>
2017-11-07 15:31:15pitroulinkissue31960 messages
2017-11-07 15:31:15pitroucreate