Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)

2007-11-15 Thread Russell Keith-Magee
On 11/15/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > > Joseph Kocherhans wrote: > > Hey Todd, I haven't looked at you patch, but here's what Russ > > mentioned when I asked: > > > >

Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)

2007-11-15 Thread Will Hardy
#!/bin/sh if [ -e "./manage.py" ] ; then ./manage.py $@ else django-admin.py $@ fi That way, new users can simply learn the mighty django command, trendy users can switch over to the mighty django command and old users can hang onto their habits and let their fingers type what they always

Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)

2007-11-15 Thread SmileyChris
On Nov 15, 6:02 pm, Gary Wilson <[EMAIL PROTECTED]> wrote: > Would it be crazy if we got rid of django-admin.py and manage.py and replaced > them with one "django" command to rule them all? Sounds great to me! --~--~-~--~~~---~--~~ You received this message

one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)

2007-11-14 Thread Gary Wilson
Joseph Kocherhans wrote: > Hey Todd, I haven't looked at you patch, but here's what Russ > mentioned when I asked: > > http://groups.google.com/group/django-developers/browse_thread/thread/fb148adb454b74ef/789da4389cf33295?lnk=gst=kocherhans+django-admin#789da4389cf33295 Would it be crazy if we