News for hackers. Stuff that matters.
Re:Plop: Low-overhead profiling for Python by bdarnell on Tuesday July 10, 2012 @06:47PM (#4226667)
Whoops. I deleted some dead code just before release but missed this import because I still had the old .pyc file lying around. I'm uploading a fixed build now.
Re:Plop: Low-overhead profiling for Python by famousactress on Tuesday July 10, 2012 @07:00PM (#4226715)
I hate that! We recursively delete .pyc files on django runservers in local development and before unit test runs in our CI environment because we got sick of being bit by exactly this error.
Re:Plop: Low-overhead profiling for Python by sdcooke on Tuesday July 10, 2012 @07:33PM (#4226850)
We've started running our runservers with pythondontwritebytecode=1 - I haven't noticed enough of a performance impact to change it back and it saves us remembering to delete pyc files before deploys.
Re:Plop: Low-overhead profiling for Python by lamby on Wednesday July 11, 2012 @11:37AM (#4229680)
You use runserver in production?
Re:Plop: Low-overhead profiling for Python by sdcooke on Monday July 16, 2012 @06:39PM (#4253061)
Definitely not! But we use it for testing locally, during which time we don't write pyc files which means we're less likely to have issues with that when we deploy to production.
Re:Plop: Low-overhead profiling for Python by heretohelp on Tuesday July 10, 2012 @07:07PM (#4226742)
Glad to be of service. Cheers. :)

Edit: Update worked. I did a pip install --upgrade plop, the spurious line is gone from my virtualenv.

Have a wonderful day, thanks for sharing this.