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 tim.peters
Recipients Carl.Friedrich.Bolz, eric.smith, fredrikj, mark.dickinson, pernici, serhiy.storchaka, steve21, tim.peters, vstinner, xuanji
Date 2022-01-30.01:41:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ha! This will never die. More discussion in bpo-46558.

Ya, I already closed it, but don't want to. I opened it to begin with to record an int->str method that doesn't use division, so it didn't really belong on this report.

What if we _didn't_ convert these things to C? That's the primary question the new report gets around to asking. These things are far easier to write, understand, and maintain in Python, and converting to C is generally only improving a constant factor, or _maybe_ removing a log(n) factor. When we're looking at massive O() improvements, squeezing those out is of comparatively little value.
Date User Action Args
2022-01-30 01:41:11tim.peterssetrecipients: + tim.peters, mark.dickinson, pernici, vstinner, Carl.Friedrich.Bolz, eric.smith, fredrikj, steve21, xuanji, serhiy.storchaka
2022-01-30 01:41:11tim.peterssetmessageid: <>
2022-01-30 01:41:10tim.peterslinkissue3451 messages
2022-01-30 01:41:10tim.peterscreate