Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)
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: > > > > http://groups.google.com/group/django-developers/browse_thread/thread/fb148adb454b74ef/789da4389cf33295?lnk=gst=kocherhans+django-admin#789da4389cf33295 > > 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? I agree with Malcolm. There's minimal benefit, but lots of existing scripts using the existing names. Russ Magee %-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)
#!/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 type. Some time in the future, when the older users have died out, you can unify the three commands, removing or renaming ./manage.py in the project directory. I think the new command makes a lot of sense to new users, and it's much easier for them to remember. Cheers, Will -- Will Hardy http://www.willhardy.com.au --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)
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 because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
one django command (was: Re: django-admin.py can't access user-supplied commands, even if --settings option is provided)
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 got rid of django-admin.py and manage.py and replaced them with one "django" command to rule them all? django startproject myproj django startapp myapp django runserver django runserver --settings myproj.settings django test [myapp ...] django selftest [django_test_app ...] and so on. Without a --settings option, settings.py is looked for in the current directory. Gary --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
