On 12/10/11 15:06, Carl Meyer wrote: > > > On 10/12/2011 07:53 AM, Russell Keith-Magee wrote: >> I'm not convinced it's a bad idea. From an pedagogical perspective, >> it's easy to explain -- Make a directory to contain all the bits for >> your project, move into the directory, then bootstrap your project. > > It's not so easy to explain why startproject can't just create the > directory to contain all the bits it creates in the first place, instead > of making me do it manually :-)
I think there could be at least one good reason - if the developer has already created a directory in which to store all the stuff, which would actually be my natural instinct especially when it comes to a new project with VCS: $ mkdir foo $ cd foo $ hg init # OK, now what am I going to put in it? Oh, a Django project. In fact, it might be good idea to encourage use of VCS by mentioning it. If I remember SVN correctly, you would actually need to think about it before 'mkdir foo' - you 'svnadmin create', then checkout the empty repo to start working. For either of these workflows, you probably wouldn't want startproject creating your main directory. I actually like the idea that Django is not supposed to be managing your entire project - rather, your project uses Django. Luke -- "Oh, look. I appear to be lying at the bottom of a very deep, dark hole. That seems a familiar concept. What does it remind me of? Ah, I remember. Life." (Marvin the paranoid android) Luke Plant || http://lukeplant.me.uk/ -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
