Ok this morning it seems that I have found the error but I am not sure
why this is.  So this morning I decided to try and svn update on my
django 96 source and after doing so. I was able to get my
functionality back. Next I decided to run my script that removes pyc
files. After doing so I again got this crazy error. So next I
proceeded with running manage.py validate  getting 0 errors and my
functionality back.  so when it validated, it recreated the necessary
pyc files that I just removed and all works again. here is a dpaste of
the script that I ran if interested: http://dpaste.com/25049/.

Having said that, you are probably wondering why I remove the pyc and
other files suchas Ds_Store. Well there is a problem somewhere along
the line when I am developing that tends to want to cache results
therefore giving me inadequate results. (and the caching module is not
enabled).  I think in some part it has to do with apache. In apache I
set the MaxRequestsPerChild   1 so that apache is forced to recreate a
new request each time. even after doing that I still seem to
experience caching problems so my quick fix is to remove the pyc
(which that doesn't always work either).  Another reason that remove
my files is for when I do an svn commit. I don't want extra crap files
being committed with that.

Anyone have further suggestions as to why this freaks out when I
remove pyc files and giving errors?  Is there a better approach to
solving or better handling the caching problem when in development
mode?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
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