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 nedbat
Recipients Sergey.Kirpichev, THRlWiTi, Trip.Volpe, ajaksu2, alex, amaury.forgeotdarc, barry, belopolsky, brett.cannon, diana, eric.araujo, eric.snow, ethan.furman, flox, nedbat, pgimeno, rhettinger, serhiy.storchaka, terry.reedy, tshepang, vstinner
Date 2018-06-02.19:43:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527968625.76.0.592728768989.issue2506@psf.upfronthosting.co.za>
In-reply-to
Content
Serhiy: thanks for the fuller story about the optimizations in place now.  I'll repeat my earlier plea: providing a way to disable optimization is beneficial for tooling like coverage.py, and also for helping us to ensure that the optimizer is working correctly.

I doubt anyone commenting here would be happy with a C compiler that optimized with no off-switch.
History
Date User Action Args
2018-06-02 19:43:46nedbatsetrecipients: + nedbat, barry, brett.cannon, rhettinger, terry.reedy, amaury.forgeotdarc, belopolsky, vstinner, ajaksu2, eric.araujo, alex, flox, THRlWiTi, ethan.furman, tshepang, eric.snow, serhiy.storchaka, diana, Trip.Volpe, pgimeno, Sergey.Kirpichev
2018-06-02 19:43:45nedbatsetmessageid: <1527968625.76.0.592728768989.issue2506@psf.upfronthosting.co.za>
2018-06-02 19:43:45nedbatlinkissue2506 messages
2018-06-02 19:43:45nedbatcreate