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 yselivanov
Recipients ArthurGoldberg, 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, yselivanov
Date 2018-10-04.00:25:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538612753.49.0.545547206417.issue2506@psf.upfronthosting.co.za>
In-reply-to
Content
Having properly working coverage tooling is simply invaluable to pretty much every serious Python user.  I support Ned's idea of adding an option to disable peephole optimizer (and similar other optimization passes).  Why is this even debated?
History
Date User Action Args
2018-10-04 00:25:54yselivanovsetrecipients: + yselivanov, barry, brett.cannon, rhettinger, terry.reedy, amaury.forgeotdarc, belopolsky, vstinner, ajaksu2, nedbat, eric.araujo, alex, flox, THRlWiTi, ethan.furman, tshepang, eric.snow, serhiy.storchaka, diana, Trip.Volpe, pgimeno, Sergey.Kirpichev, ArthurGoldberg
2018-10-04 00:25:53yselivanovsetmessageid: <1538612753.49.0.545547206417.issue2506@psf.upfronthosting.co.za>
2018-10-04 00:25:53yselivanovlinkissue2506 messages
2018-10-04 00:25:52yselivanovcreate