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 alex, arigo, georg.brandl, gvanrossum, pitrou, rhettinger, serhiy.storchaka, steven.daprano, tim.peters, vstinner
Date 2014-07-17.03:10:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm afraid "microoptimizations" aren't worth measuring to begin with, since, well, they're "micro" ;-)  Seriously, switch compilers, compilation flags, or move to a new release of a single compiler, and a micro-optimization often turns into a micro-pessimization.  If I _want_ to measure something unrolled, I'll unroll it myself.  But since I almost never want to measure something unrolled anyway, an option to do so would just be "yet another attractive nuisance" to me.
Date User Action Args
2014-07-17 03:10:49tim.peterssetrecipients: + tim.peters, gvanrossum, arigo, georg.brandl, rhettinger, pitrou, vstinner, steven.daprano, alex, serhiy.storchaka
2014-07-17 03:10:49tim.peterssetmessageid: <>
2014-07-17 03:10:49tim.peterslinkissue21988 messages
2014-07-17 03:10:49tim.peterscreate