➜

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 Timothy.Fitz
Recipients Timothy.Fitz, afriesen, brett.cannon, pitrou, rhettinger
Date 2010-04-12.23:52:44
SpamBayes Score 8.610172e-06
Marked as misclassified No
Message-id <1271116366.04.0.210785650032.issue8379@psf.upfronthosting.co.za>
In-reply-to
Content 
In this case bytecode isn't an optimization, it's a distribution choice (this bug reared it's ugly head in our closed-source downloadable client).

I think that implausible execution paths are still a bug. 

Running a .pyo without -O should be explicitly an error. For instance can we change python to reliably blow up at import time? Or implicitly run as if you added -O?
History
Date User Action Args
2010-04-12 23:52:46Timothy.Fitzsetrecipients: + Timothy.Fitz, brett.cannon, rhettinger, pitrou, afriesen
2010-04-12 23:52:46Timothy.Fitzsetmessageid: <1271116366.04.0.210785650032.issue8379@psf.upfronthosting.co.za>
2010-04-12 23:52:44Timothy.Fitzlinkissue8379 messages
2010-04-12 23:52:44Timothy.Fitzcreate