Thinkhole Labs

Hopfully this will be my last post related to my previously broken Django install.

As per Adrian’s suggestions (see comments), I looked for any .pyc files in the Django and removed them as follows:

metis# cd /usr/local/django/django_src/django
metis# find -name "*.pyc" | xargs rm
Python scripts get compiled into bytecode (.pyc) files when they are run, but these files are not managed by SVN. So that can cause problems when performing updates.

Unfortunately, however, this did not fix my problem…

Starting over

At that point I figured that since I wanted to move everything around anyway (i.e. put all my Django stuff in /usr/local/django), I figured I’d just delete and reload the Django source files. Sounds good, right?

After removing the project files, I noticed I will still getting the same Django errors. Then I removed the Django source files… all of them. But I was still getting the same Django errors.

(At this point, those smarter than me will see where this is going.)

Resolution

Apparently mod_python (and Django?) does some fancy caching, so I probably only needed to restart Apache after doing the svn update. But by the time I realized that I had already dropped the database and removed all my project files… Doh!

So although I can not confirm that an Apache restart would have fixed my problems, I am quite sure that was the issue.

Not a problem though, because it gave me a chance to move all my Django files to where I want them and run through the first part of the tutorial again. It’s been a great learning experience, and now I hope to finish the rest of the tutorial this week.

Again, thanks go to Adrian for taking time to offer help and advice. That speaks volumes about the quality of people working on the Django team.