New approach at http://code.google.com/p/django-reusableapps/

Dont miss my weblog at http://jannisleidel.com

##########################################################################################

Please download django-package.diff and patch the current django trunk with it.

wget http://django-package.googlecode.com/svn/trunk/django-package.diff
cp django-package.diff /path/to/django_src
cd /path/to/django_src
patch -p0 < django-package.diff

You can use one new command with django-admin.py to create a standalone application package. You should do this in a blank directory, outside the directory where you manage your other django applications. For now it's best to develope every application in a seperate directory since each should be installed with setuptools easy_install afterwards.

Revision 17:

• again MAJOR overhaul of the code to use more OOP idioms (hell, it's Python!)
• better handling of user inputs
• extensible prompt system, including variable validation
• only the changed files will be saved when running editapp, except for the txt files (which will never be overwritten)
• more docstrings
• wrapping of setuptools' setup() to make sure the default PyPI keyword is included anytime

Revision 15:

• incompatible changes after major refactoring of django.core.management
• docstrings
• check for invalid app names (like "tests", "doc" etc)
• added the question if the app can be zipped (as an egg)
• use of CommandError from django.core.management.base
• new reusable applications are now created in a directory with the name of the app, "editapp" still needs to be executed within the application directory and needs the name of the app

# tree myapp/
myapp/
|-- INSTALL.txt
|-- MANIFEST.in
|-- README.txt
|-- docs
|-- entries
|-- format
|-- myapp
|   |-- __init__.py
|   |-- models.py
|   |-- templates
|   |   `-- myapp
|   `-- views.py
|-- release.py
|-- setup.py
`-- tests

Revision 9:

Changed a lot on the release engine:

• better renaming
• in the meta data assistent new question for keywords (needed for the Django application repository)
• rewritten template system for the skeleton files
• code clean-up

Revision 8:

Fixed application name changing (either with a fresh or with an existing application) and the automatic directory move

I changed with revision 7 the default behaviour of the "startapp" command!

Last changelog:

Greatly enhanced "startapp" and a new "editapp" command to re-edit the meta information in the release.py.
Error handling: a lot.
New "--noskeleton" for "startapp" command and changed behaviour when creating a Django application with it:
it now creates a STANDALONE apps with the skeleton files defined in django.utils.package.
With the help of "--noskeleton" switch it's still possible to create plain project based apps.