Seconds ago I got this running and haven't yet fully understood what I've just done but the results are exactly what I need and this is going to be great.

Basically, in Django you have views like this:

Now in my unit tests I don't want to have to call the view function and then have to dissect the resulting HTML just to figure out if the view function prepared the correct variables. So, here's my solution to this problem:

From the django-users mailinglist which I'm becoming more and more helpful in:

 > Could you share approximately how big your project is? I know it's
 > hard to find a real measure for this, but how about number of database
 > tables?

 A project I worked on over the summer used a Database that was 130
 tables, and getting 1gb updates every 2 minutes. I was witting a new
 web app to do calculations on the data and the company wanted to use
 Java since thats what they knew best and had spend huge amounts of
 money (1 mil +) to support with Sun Servers, and such. But I knew
 python and django would be a better fit for this particular app, but
 the boss wouldnt listen. So we had 10 Developers working on the Java
 version (Including me) and over 3 months we got it about 85% done,
 though it had no unit tests. During the same three months, I worked on
 my own time after work and basically had no life for the whole time, I
 was able to get the web app 100% complete with unit tests. That
 convinced my boss that Django was a good fit.

 The site is an internal app that I cannot give access to (And I
 actually had to get permission to give what info I have), but I can
 say that Django is a suitable framework for what you are looking for. 

Christ! 10 developers and no unit test!? Someone should remind them that you don't write unit tests for your bosses pleasure but for your own sanity and productivity.

I know that this quote is totally unscientific since Dj, as he says, can't back it up but it's a story interesting enough.

I've been working with Django a lot lately and while I can't contribute to the code base until my project is done, I can contribute money.

Been browsing the Django mailinglist and found this guy (link above) and some other people saying they're willing to donate money towards the OS effort that is Django. That's nuts and is a failed practice but it does mean a lot. Zope had this about 4-5 years ago too but that was then. Clearly the heat is all on Django (and Rails admittedly) at the moment. Well done to all involved!

I've been doing quite a bit of Django this weekend and this instant quick rush I got from getting started has gone off and now starts to become just normal trudging. At the moment it's the templating language that annoys the hell out of me.

In conclusion: Today Django won another point in the race for my attention.