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 asvetlov, jimmylai, pitrou, vstinner, yselivanov
Date 2018-05-22.13:40:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526996429.17.0.682650639539.issue33521@psf.upfronthosting.co.za>
In-reply-to
Content
> @pitrou We'll measure the wins of gather when we implement it in C. Before that, we need to get all helpers ready in C.

You don't have to provide _asyncio.isfuture() (in C) to implement gather() in C.

If your goal is to optimize gather(), write a change to only implement gather() no?

What's the point of optimizing isfuture() is gather() is implemented in C and doesn't call the Python implementation anymore?

Implement isfuture() is C and expose it as _asyncio.isfuture() are two different things.
History
Date User Action Args
2018-05-22 13:40:29vstinnersetrecipients: + vstinner, pitrou, asvetlov, yselivanov, jimmylai
2018-05-22 13:40:29vstinnersetmessageid: <1526996429.17.0.682650639539.issue33521@psf.upfronthosting.co.za>
2018-05-22 13:40:29vstinnerlinkissue33521 messages
2018-05-22 13:40:29vstinnercreate