Django Packages solves the problem in the Django community of being able to easily identify good apps, frameworks, and packages. Ever want to know which is the most popular or well supported Django blog, content management system, or api tool? Django Packages solves that problem for you!

A Django package is anything that is involved in the Django ecosphere that can be stored on a repository such as Github or Bitbucket. If it can be stored in Pypi thats even better!

The site is live and functional at http://www.crisishacks.com.

Grids let you compare Django packages to each other. A grid comes with a number of default items compared, but you can add more features in order to get a more specific comparison.

We are trying out Django Packages without the traditional tagging system, because we think that grids give us a lot more specificity.

The fixtures provide four categories: apps, frameworks, projects, and utilities.

Not yet. Django Packages was cooked up during Django Dash 2010. We wanted to keep the scope of our work reasonable. We'll try and include those sites in the future. We also want to include other package repo systems over time.

Django Packages does support Github and Bitbucket. Launchpad is next. Google Project Hosting may not happen because of a lack of a formal API.

In production add symlinks to the pinax and uni_form media directories:

cd media
ln -s ../../env-crisishacks/lib/python2.6/site-packages/pinax/media/default/pinax/ pinax
ln -s ../../env-crisishacks/lib/python2.6/site-packages/uni_form/media/uni_form/ uni_form

Change your settings.py file to point to prod.db then do:

python manage.py syncdb

python manage.py runserver

python manage.py loaddata test_initial_data

You can update all the packages with the following command:

python manage.py package_updater

For Django Dash 2010, @pydanny and @audreyr were scared of rabbits.