➜

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 yselivanov
Recipients giampaolo.rodola, gvanrossum, pitrou, yselivanov
Date 2017-11-07.15:57:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510070255.89.0.213398074469.issue31960@psf.upfronthosting.co.za>
In-reply-to
Content 
> Just try the snippet :-) If you want to see it finish in a finite time, move the future instantiation inside the coroutine.

Yeah, I see the problem.  OTOH your proposed change to lazily attach a loop to the future isn't fully backwards compatible.  It would be a nightmare to find a bug in a large codebase caused by this change in Future behaviour.  So I'm -1 on this idea, that ship has sailed.

> Unfortunately that's not possible in our case.  Short version: we are using Tornado which creates a asyncio Future eagerly, see https://github.com/tornadoweb/tornado/blob/master/tornado/locks.py#L199

Maybe the solution is to fix Tornado?
History
Date User Action Args
2017-11-07 15:57:35yselivanovsetrecipients: + yselivanov, gvanrossum, pitrou, giampaolo.rodola
2017-11-07 15:57:35yselivanovsetmessageid: <1510070255.89.0.213398074469.issue31960@psf.upfronthosting.co.za>
2017-11-07 15:57:35yselivanovlinkissue31960 messages
2017-11-07 15:57:35yselivanovcreate