id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
17503	startproject can't create new project directly in current working directory	Carl Meyer	Carl Meyer	"The current fix for #17042, although it allows more flexibility with regard to where `startproject` and `startapp` create the new app/project, doesn't actually meet the original use case that motivated that ticket. Several people (including at least one or two core devs) had [http://groups.google.com/group/django-developers/msg/4d155579ab98c536 expressed the wish] to be able to take an existing directory that they had already created (for instance, initialized as a vcs repo) and convert it into a stock Django project using `startproject`. But the current implementation of the optional second argument to `startproject` doesn't allow you to ever reuse an existing directory, it always creates a new one and just allows you to specify where it will do so. To make it clearer with an example:

Current behavior:
{{{
$ mkdir /home/carljm/target
$ django-admin.py startproject someproj /home/carljm/target
$ tree /home/carljm/target/
/home/carljm/target/
`-- someproj
    |-- manage.py
    `-- someproj
        |-- __init__.py
        |-- settings.py
        |-- urls.py
        `-- wsgi.py

}}}

Desired behavior:
{{{
$ mkdir /home/carljm/target
$ django-admin.py startproject someproj /home/carljm/target
/home/carljm/target/
|-- manage.py
`-- someproj
    |-- __init__.py
    |-- settings.py
    |-- urls.py
    `-- wsgi.py
}}}

Jannis (author of r17246, the fix for #17042) agreed on IRC that this behavior could be changed to meet the original use case."	Bug	closed	Core (Management commands)	1.3	Normal	fixed			Accepted	0	0	0	0	0	0