3 ms·

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 no

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.

famousactress 14y ago
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.
- sdcooke 14y ago
  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.
  - lamby 14y ago
    You use runserver in production?
    - sdcooke 14y ago
      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.
heretohelp 14y ago
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.
deleted 14y ago
[deleted]