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 Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov
Date 2015-08-02.16:48:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438534090.83.0.155217234923.issue24383@psf.upfronthosting.co.za>
In-reply-to
Content
[Repeat from the review]

I still don't think this should be done for 3.5.0, it's definitely a feature, and there are no more betas planned (rc1 is next weekend).

We may be able to do this for 3.5.1 (since PEP 492 was accepted provisionally, see https://mail.python.org/pipermail/python-dev/2015-May/139844.html) although it's still a pretty big new feature.

We should also have more discussion (on python-dev, IMO, not just in the issue) about whether we want this at all -- I find it questionable to mix await and threads, as I have said several times in the discussion about Nick Coghlan's proposal to introduce helper functions with a similar function.

The argument "but they're both Futures" seems pretty bogus to me.
History
Date User Action Args
2015-08-02 16:48:10gvanrossumsetrecipients: + gvanrossum, scoder, vstinner, alex.gronholm, Yury.Selivanov, yselivanov
2015-08-02 16:48:10gvanrossumsetmessageid: <1438534090.83.0.155217234923.issue24383@psf.upfronthosting.co.za>
2015-08-02 16:48:10gvanrossumlinkissue24383 messages
2015-08-02 16:48:10gvanrossumcreate