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, methane, mpaolini, serhiy.storchaka, vstinner, yselivanov
Date 2016-08-09.23:30:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470785450.77.0.286368393571.issue26081@psf.upfronthosting.co.za>
In-reply-to
Content
> What parts of Future are performance critical? Maybe it is worth to implement in C only the most critical code.

Basically everything.  Contrary to @contextmanager, Futures are the building blocks of asyncio, so instantiation + awaiting on them + setting results must be fast.

To cover instantiation, I want to add a freelist for Futures, so this basically requires them to be implemented in C (and it's not a lot of C code actually).
History
Date User Action Args
2016-08-09 23:30:50yselivanovsetrecipients: + yselivanov, gvanrossum, vstinner, giampaolo.rodola, methane, serhiy.storchaka, mpaolini
2016-08-09 23:30:50yselivanovsetmessageid: <1470785450.77.0.286368393571.issue26081@psf.upfronthosting.co.za>
2016-08-09 23:30:50yselivanovlinkissue26081 messages
2016-08-09 23:30:50yselivanovcreate