The most valuable thing I got from attending Djangocon last week was a giant list of technologies. Some we already use at Mahalo (it was nice to hear that we were doing something right), and some that I hadn’t heard of before. Here’s the list, hope it helps you find something useful:

django-config – a project aimed at working with profiles for multiple settings files. haystack – a search app for Django brabeion – an app for adding badges to your project zeromq – not a Django thing, but I heard this mentioned on several occasions. I still don’t understand exactly what it is, so check it out. (Not to be confused with RabbitMQ or any AMQP servers.) ipython – a better python shell. You should be using this. maatkit – tools for managing MySQL, Postgresql, and memcached databases. sqlalchemy – an alternate python ORM. django_alfajor – a Django wrapper for using alfajor, a functional front-end testing framework in Python. dulwich – git protocol and file formats written in Python. sphinx – Python documentation generator. celery – a tool for asynchronous job/task processing. fabric – python library and tool for deployment via SSH. gunicorn – a lightweight WSGI HTTP server in Python. django-piston – a framework for creating a RESTful API for your Django project. django-tastypie – another framework for adding a RESTful API to your Django project. django-taggit – a Django tagging app. django-debug-toolbar – a great toolbar/heads-up-display for debugging and developing in Django. django-filter – a tool for generically building Querysets based on user inputs. django-notification – a user notification tool. logbook – logging replacement for Python/Django proclaim – a tool using Redis to allow conditional rollout of features. varnish – a page caching solution. django-staticfiles – an app to help serving static files in Django. lettuce – a tool for managing test-driven development. Edit: sentry – dammit, I forgot this one. Real-time logging for Django exceptions. (We just started using this one, it’s pretty sweet.)

No promises on the quality of these (although most of them are pretty widely used, but a few of them were people’s pet projects, so they’re still in beta or alpha.

Also, if you want to read a much more thorough overview of 2010 Djangocon, check out this post: http://birdhouse.org/blog/2010/09/13/djangocon-2010/