What's new? | Help | Directory | Sign in
Google
django-package
package management for django (GSoC 2007 project)
  
  
  
  
    
Show all Featured Wiki Pages:
Usage
Join project
Project owners:
  leidel, ubernostrum

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:

Revision 15:

Revision 9:

Changed a lot on the release engine:

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.