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 rhettinger
Recipients Trip.Volpe, ajaksu2, amaury.forgeotdarc, barry, belopolsky, eric.araujo, eric.snow, ethan.furman, flox, nedbat, rhettinger, terry.reedy, tshepang, vstinner
Date 2014-05-22.22:21:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400797319.69.0.789524553336.issue2506@psf.upfronthosting.co.za>
In-reply-to
Content
[Victor]
> Oh, another option to solve the .pyc file issue is to *not* 
> write .pyc files if the peephole optimizer is disabled. 
> If you disable an optimizer, you probably don't care of performances.

That is an inspired idea and would help address one of the possible problems that could be caused by a new on/off switch.
History
Date User Action Args
2014-05-22 22:21:59rhettingersetrecipients: + rhettinger, barry, terry.reedy, amaury.forgeotdarc, belopolsky, vstinner, ajaksu2, nedbat, eric.araujo, flox, ethan.furman, tshepang, eric.snow, Trip.Volpe
2014-05-22 22:21:59rhettingersetmessageid: <1400797319.69.0.789524553336.issue2506@psf.upfronthosting.co.za>
2014-05-22 22:21:59rhettingerlinkissue2506 messages
2014-05-22 22:21:59rhettingercreate