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 rhettinger
Recipients brett.cannon, pablogsal, rhettinger, serhiy.storchaka, tim.peters
Date 2019-06-15.17:45:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560620731.75.0.281101150653.issue37271@roundup.psfhosted.org>
In-reply-to
Content
Tim, do you have any thoughts on this?

In the past, there was an implicit red-line that we would not cross even if a performance improvement was possible.  Given that that was a long time ago and that the newer devs are both more aggressive and more fearless, we ought to re-examine whether the red-line should be made explicit or whether it no longer applies.

For this particular patch, a source of discomfort is that the optimization step takes longer (due to multiple passes).  So, we sometimes get faster wordcode but that time it takes to get there is longer.
History
Date User Action Args
2019-06-15 17:45:31rhettingersetrecipients: + rhettinger, tim.peters, brett.cannon, serhiy.storchaka, pablogsal
2019-06-15 17:45:31rhettingersetmessageid: <1560620731.75.0.281101150653.issue37271@roundup.psfhosted.org>
2019-06-15 17:45:31rhettingerlinkissue37271 messages
2019-06-15 17:45:31rhettingercreate