Good list. Nothing on there that I haven't seen or heard about before, but it's good for people just starting out in Django.

For reference, the bible for finding stuff like this in the Django community is: http://djangopackages.com/

I've been keeping my eye on DjangoPackages for a while, and while I think it's a great community resource - I am not a Django-dev so I can't comment more than that - the UI seems haphazard at best.

Wow, With this arsenal, I need to give Django another try.

That link is extremely helpful. Thx.

How did django-annoying (https://bitbucket.org/offline/django-annoying) not make the list? I find the stuff in django-annoying to be crucial on any Django project I do (the render_to() and @ajax_request decorators especially).

If you like render_to, you might also like TemplateView http://django.me/TemplateView Class Based Views are awesome when you get the hang of them.

I tested out the class based views in Django 1.3, but decided that I didn't like the complexity that all the MixIns added. I was constantly having to remember which things each MixIn added to my class. I found it simpler to just do function based views with several decorators.

Just a little heads up for Django newcomers. Don't install Django with apt. The official Git repo is best so you can get the latest bug fixes. If you want a turn-key solution, use Pip.

Don't you mean the official SVN release?

https://docs.djangoproject.com/en/1.3/topics/install/#instal...

I believe all the Git repos are just mirrors of SVN.

I prefer GIT, so I recommend GIT. I see no need to turn this into a SVN vs GIT discussion.

I'm a Git user too, so no flaming: I just feel it's best to get source code from the original source in case the mirror isn't up to date for whatever reason.

The official GIT mirror found at http://github.com/django/django/ is automatically updated every 5 minutes.

People used to do this before, but most have finally started using the versioned releases. It makes things easier for everyone. You shouldn't use Django trunk in production unless you have a very good reason to.

On the projects I am working on, we have encountered bugs in the Django 1.3 stable release. So, based on my own experience, I recommend using Django trunk (with extensive testing of course).

This really is quite a superb list. I just need to clone myself to find time to try some more - perhaps a collaborator will help... with Rails, PHP, Grails in use at the moment, one more language may just blow a socket. Thanks for posting.

I'm a little disappointed that he mentioned a tool he built on top of Fabric but then didn't even mention Fabric until the final item.

It's a list. Something has to be last. If he had left it out then it would be cause for complaint.

In his defense, Fabric is not django specific.Though it is pretty nice.

Great list, we use a lot of these.

Does anyone know if there is a project that makes it easier to white label your app's services?