Yes! Actually I also bumped into the annoying `ImportError: No module named django.core` problem, so fixing virtualenv would be a blessing. *But.. *I still think this is the wrong path, since python setuptools has a better solution for that with cross platform compatibility etc. Take a look at https://github.com/TurboGears/tg2devtools/blob/master/setup.py *vs * https://github.com/django/django/blob/master/setup.py you can see that Turbogears (as well as almost any other python webframework or commandline tool) uses setuptools entry points to establish a commandline script (under the working scripts/bin folder, according to the platform). why wouldn't Django do that? and then solve both problems in one shoot?
On Friday, March 1, 2013 8:25:50 PM UTC+2, Alon Nisser 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. > > thanks for the clarification > > -- 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.
