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-26.00:10:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CA+3bQGGo9=MDF_zK=bVSozuDAmz+F7-g-NtSEdFMGF2ibk0jwg@mail.gmail.com>
In-reply-to <1527270151.11.0.682650639539.issue33521@psf.upfronthosting.co.za>
Content
I disagree with your rationale. At least, it is not how we decide to
optimize something or not in Python. Python is first made of people who
will have to maintain the code for the next 5 years if not longer. C code
is harder to maintain than Python code.

A significant speedup on a microbenchmark is nice, but asyncio still lacks
a more general benchmark suite...

I have no opinion on this specific optimisation.
History
Date User Action Args
2018-05-26 00:10:45vstinnersetrecipients: + vstinner, pitrou, asvetlov, yselivanov, jimmylai
2018-05-26 00:10:45vstinnerlinkissue33521 messages
2018-05-26 00:10:44vstinnercreate