Re: Should manage.py startapp create a urls.py file?

2008-02-11 Thread Empty
Rob, If you want, check out the django-command-extensions project on Google Code (http://code.google.com/p/django-command-extensions/). I added a create_app command extension that allows you to use a --template option for specifying your app directory structure. If no template is provided a

Re: Should manage.py startapp create a urls.py file?

2008-02-04 Thread Alex Koshelev
No, only startproject creates project-wide urls.py On 4 фев, 20:53, "Rob Hudson" <[EMAIL PROTECTED]> wrote: > If it's common advice to make apps portable and bundle urls along with > an app, shouldn't manage.py startapp also drop in a default urls.py > file? > > I realize it's simple to create a

Re: Should manage.py startapp create a urls.py file?

2008-02-04 Thread Brian Rosner
> If it's common advice to make apps portable and bundle urls along with > an app, shouldn't manage.py startapp also drop in a default urls.py > file? -1. While Django is a web framework it would seem logical for a urls.py to be created with startapp. However, I am sure the original design

Should manage.py startapp create a urls.py file?

2008-02-04 Thread Rob Hudson
If it's common advice to make apps portable and bundle urls along with an app, shouldn't manage.py startapp also drop in a default urls.py file? I realize it's simple to create a skeleton file yourself, but if manage.py did it, it's one less thing to think about and do, and also promotes good