Opened 17 years ago
Closed 17 years ago
#5856 closed (invalid)
Crazy caching of code with mod_python
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 0.96 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi, all!
I see crazy caching of code after migration to mod_python.
I'd turned on debug, and see.
Sometimes djando project works fine. But sometimes it takes old code!
I see errors in urls.py which were corrected yesturday!!!
How is it possible?
I'd checked twice file urls.py. But when error occurs I see old file urls.py? WHere does it take it? May be there is some django code cache, so it sometimes takes code from there?
The most interesting thing - I don't see such behavior using fastcgi!
If I kill process and it was restarted it is completely new.
Change History (2)
comment:1 by , 17 years ago
Version: | SVN → 0.96 |
---|
comment:2 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This is the expected behavior of mod_python. Your code is loaded into memory and won't be refreshed until the server is restarted. This isn't anything Django is doing. It is how Python works. It is also stated here http://www.djangoproject.com/documentation/modpython/#running-a-development-server-with-mod-python
I'm sorry - I use 0.96.1 version.