➜

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 loewis
Recipients Boris.FELD, collinwinter, ezio.melotti, flox, loewis, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2012-04-27.15:31:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335540699.89.0.550929644697.issue13621@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm closing this as "won't fix". The only way to get back the exact performance of 3.2 is to restore to the 3.2 implementation, which clearly is no option. I don't consider performance regressions in micro benchmarks inherently as a bug.

If there is a specific regression which people think constitutes a real problem, a separate bug report should be submitted.
History
Date User Action Args
2012-04-27 15:31:39loewissetrecipients: + loewis, collinwinter, pitrou, vstinner, ezio.melotti, flox, Boris.FELD, python-dev, serhiy.storchaka
2012-04-27 15:31:39loewissetmessageid: <1335540699.89.0.550929644697.issue13621@psf.upfronthosting.co.za>
2012-04-27 15:31:39loewislinkissue13621 messages
2012-04-27 15:31:39loewiscreate