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 Julian
Recipients Julian, brett.cannon, ezio.melotti, lennartyseboodt, ncoghlan, pitrou
Date 2011-12-04.00:24:06
SpamBayes Score 2.6496894e-08
Marked as misclassified No
Message-id <1322958247.14.0.372907187746.issue13523@psf.upfronthosting.co.za>
In-reply-to
Content
I know this is a feature, and on occasion as pointed out a useful one. But in some cases it can be a tad annoying as the OP probably considered it.

I had a recent example where a lingering .pyc made my test suite pass (and me nearly push broken code) despite the fact that I'd moved the file away and edited it, with bugs. Obviously I now remember to rebuild and remove all .pyc's before I commit, but it took a near miss to remind me to.

Would it be useful to have a command line flag that did something like this (perhaps that test runners could set by default) to prevent others from running into similar situations?
History
Date User Action Args
2011-12-04 00:24:07Juliansetrecipients: + Julian, brett.cannon, ncoghlan, pitrou, ezio.melotti, lennartyseboodt
2011-12-04 00:24:07Juliansetmessageid: <1322958247.14.0.372907187746.issue13523@psf.upfronthosting.co.za>
2011-12-04 00:24:06Julianlinkissue13523 messages
2011-12-04 00:24:06Juliancreate