Closed GoogleCodeExporter closed 8 years ago
Right, what about using 'manage.py' for checking a valid project root is found ?
Maybe the entire (double) check could even be dropped. As the first code file
on the
stack should be in the project root. If that's not the case anything (unless
given by
a convention DJANGO_PROJECT_ROOT anyone ? :) could be the project root.
Original comment by v.oostv...@gmail.com
on 22 Sep 2008 at 11:28
I would just look at settings.SETTINGS_MODULE, and avoid the frame-hacking
altogether. Here's a patch.
Original comment by carl.j.meyer
on 22 Sep 2008 at 2:22
Attachments:
absolutely right, i didn't know settings.SETTINGS_MODULE existed.
Original comment by v.oostv...@gmail.com
on 26 Sep 2008 at 8:27
note-to-self; also add:
* -p,--path optionally specificy a path instead of PROJECT_ROOT
* -a,--all optionally walk all the INSTALLED_APPS and clean/compile those which are
not in the PROJECT ROOT
Original comment by v.oostv...@gmail.com
on 26 Sep 2008 at 8:32
fixed in svn
(also implemented -p)
Original comment by v.oostv...@gmail.com
on 2 Oct 2008 at 12:42
Original issue reported on code.google.com by
carl.j.meyer
on 20 Sep 2008 at 10:24