Opened 6 years ago

Closed 6 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: UI/UX:


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 which were corrected yesturday!!!
How is it possible?
I'd checked twice file But when error occurs I see old file 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.

Attachments (0)

Change History (2)

comment:1 Changed 6 years ago by anonymous

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from SVN to 0.96

I'm sorry - I use 0.96.1 version.

comment:2 Changed 6 years ago by brosner

  • Resolution set to invalid
  • Status changed from new to 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

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.