NickSergeant

One thing that Pete and I have learned is that developers can't remember every scrap of syntax that crosses their keyboard.

The hundreds of programming languages out there leave little wonder as to why this is.

Now, there's a compelling way to keep those bygone commands close at hand.

I've done a couple of Django apps so far, and one thing that always annoys me is having to manually set DEBUG in my settings.py when moving from development to production, or vice versa.

Since I'm always developing on my localhost, I know that I always want DEBUG to be True when running on localhost. I also know that DEBUG should always be False when running on my production server. Fortunately, Python makes quick work of this. In your settings.py file:

About a week ago, I released my first Django project, Finisht.com, to the general public. Surprisingly, I've received a stunning amount of enthusiasm and excitement around the product. Along with that great response came many suggestions for feature improvements. Today, I've decided to open source the project to allow anyone download, install, and improve the app.

If you're like us, you finish tasks assigned to you from several sources – email, bug trackers, support tickets, face-to-face interactions, etc. It's often difficult to find a list of all the things you've done. Finisht.com attempts to solve this problem.

When I first set out to install Django on my Media Temple server running under mod_python, I ran into a few gotchas. Luckily, there are lots of people who've tried the same thing and were successful. Unfortunately, however, those tutorials and discussions are scattered all over the place, and there really is no definitive guide to installing Django on a (mt) Media Temple DV.