On 10/26/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > > I looked around in the various tickets and threads for the reasoning > behind this, and wasn't able to find anything. Is there a particular > reason django-admin.py doesn't load custom commands? Changing this > line [1] makes everything work fine in my tests. > > Is it just that it would require you to specify settings? (via > --settings or $DJANGO_SETTINGS_MODULE)
There are two minor differences between django-admin and manage.py: manage.py disables the startproject command, and adds the startapp command. At present, the decision as to whether to remove startproject and add startapp is based entirely on which script was invoked (django-admin or manage). However, it would make good sense for this distinction to be made based on whether a settings file was available. I can't think of any reason that 'django-admin.py --settings=foo.settings' should be any different to running 'manage.py' in the foo project. Russ %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
