I had fiddled with Django before. At version 0.96 to be precise. After the release of version 1.0 I immediately got the jibbies to try it out.
After some careful deliberation I decided to install Django 1.0 on a virtual private server I had creeping around.
This machine runs Debian 4.0. This comes with version 2.4 of Python. Something I wanted to get rid off. Strangely enough the only way to do this was by going into /usr/bin and removing python and copying python2.5 back. This brings along numerous problems. For example: apt-get install python-mysql installs the MySQLdb module, but only for 2.4 so I had to install that one manually, just like I had to install Django manually. Update-alternatives did not bring any easy fix as it just cried about not having alternatives for Python. So far for my pleasant Debian experiences.
After my install and all my python/mysql troubles cleared away I immediately got a project running in my home directory. Woops, I forgot to specify the IP address for the Django development server to listen on, this took me another 15 minutes to find and some pleasant help by a guy on #debian in irc.freenode.org.
Currently I still need to configure Django to run through WSGI on my Apache webserver.
However I have already played around with Django quite a bit. I like it! It’s fun and I can really see some improvements since version 0.96. I like the decoupled admin models and so much more. I also see some might be opportunities to use Django in one of my office projects. Something I’m going to talk about at the office when I get back there.
Next time I’ll write about Django it will probably be me bitching about how to configure WSGI/Python/Django on my VPS.