That's a bit creepy. If not the DEBUG issue, then what? The parent
Apache process hasn't budged from 3MB since the restart and I can't
imagine what else would have changed between the 90MB period and the
30MB period. I loaded my project from svn so there were no .pyc files
initially, I've never used the built-in dev server, and I didn't
delete the .pyc files when I restarted Apache so I doubt that's made
any difference.

On Jun 2, 6:41 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> The problem with that hypothesis is that mod_python in the Apache
> parent process never actually imports any of your user code modules
> for Django, that is only ever done in the child processes. Thus, there
> is no way it could have remembered the setting in the first place.
> This is why I couldn't understand why your Apache parent process was
> so big, as it effectively doesn't do that much.
>
> One possibility for child processes being so big is that for some
> reason Python was loading the .pyc file for the settings file and it
> was produced from settings.py when DEBUG=True was set but for some
> reason when it was set to DEBUG=False the .pyc file wasn't regenerated
> and Python was still using it for some reason.
>
> Thus, as a precaution, it may be advisable to delete all .pyc files if
> you have run the development Django server and then subsequently using
> Apache on the same files. This would especially be required if you had
> copied all the .py/.pyc files from another box and not preserved date/
> time stamps as the copy would have set the .py/.pyc files to be the
> same and thus Python wouldn't realise the .py file was actually newer.
> Do note that although Python running as used by mod_python will
> use .pyc files, it will not replace them if Apache runs as a user
> different to the owner of the directories/files.
>
> Graham


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to