On Fri, Mar 1, 2013 at 1:25 PM, Alon Nisser <[email protected]> wrote: > and then it could be called as `django-admin somecommend` instead of `python > django-admin.py somecommand`. > since python (using setuptools entry points) makes making a python script > into a shell script quite easy I guess this has been Discussed before but I > didn't find the discussion and the explanation why doesn't Django team deem > this path worthy. > I think most python web frameworks use some kind of a shell script (or using > a customized paster/gearbox to provide this functionality) except for > Django.
django-admin.py is already an executable script. So you don't need `python django-admin.py somecommand`, just `django-admin.py somecommand` should suffice. The .py suffix is a bit ugly, to be sure, but it's not worth breaking every single introductory tutorial on the web to fix. Besides, it does have some merit as it is consistent with `./manage.py somecommand`, which is the recommended way to run pretty much every command except "startproject". Best, Alex Ogier -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
