➜

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 NeilGirdhar, Rosuav, belopolsky, ethan.furman, gvanrossum, ncoghlan, python-dev, r.david.murray, rhettinger, schlamar, scoder, serhiy.storchaka, vstinner
Date 2015-05-06.00:18:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430871519.82.0.866015043761.issue22906@psf.upfronthosting.co.za>
In-reply-to
Content 
Would it be possible to push the first part of the implementation (without __future__) just to unblock the implementation of the PEP 492 (issue #24017: async/await)?

Later push the second part for __future__.
History
Date User Action Args
2015-05-06 00:18:40vstinnersetrecipients: + vstinner, gvanrossum, rhettinger, ncoghlan, belopolsky, scoder, r.david.murray, ethan.furman, python-dev, schlamar, Rosuav, serhiy.storchaka, NeilGirdhar
2015-05-06 00:18:39vstinnersetmessageid: <1430871519.82.0.866015043761.issue22906@psf.upfronthosting.co.za>
2015-05-06 00:18:39vstinnerlinkissue22906 messages
2015-05-06 00:18:39vstinnercreate