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 brett.cannon
Recipients brett.cannon, xiang.zhang
Date 2017-01-11.18:42:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Since optimizations uses PGO which should do a fresh run, that's why there's the clearing of the state.

I'm personally not bothered by it as you really should only being doing an optimized build once when you do the first install and then you're done. But if or anyone else can come up with a way to not clear out the results while not accidentally using stale PGO-collected stats or builds then I don't see why we can't speed it up.
Date User Action Args
2017-01-11 18:42:00brett.cannonsetrecipients: + brett.cannon, xiang.zhang
2017-01-11 18:42:00brett.cannonsetmessageid: <>
2017-01-11 18:42:00brett.cannonlinkissue29243 messages
2017-01-11 18:42:00brett.cannoncreate