Opened 13 years ago
Closed 13 years ago
#16530 closed New feature (wontfix)
manage.py runserver should remove all pycs on startup
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 1.3 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | yes |
Description
I frequently run into errors where pyc files aren't being regenerated after the .py files have been changed through version control. Be nice to have manage.py runserver, which is a debug interface, remove pyc files every time it starts.
Note:
See TracTickets
for help on using tickets.
Sounds to me like you have a problem with your version control interface. Any datestamp change to a .py file should cause the .pyc file to be regenerated. There are a couple of annoying edge cases around deletion of modules, but that's part of the Python ecosystem. For me, the solution here is for you to work out what is going on with your version control system, not to make Django behave in a different way to Python.