David Ascher wrote: > On 11/17/05, Tim Keating <[EMAIL PROTECTED]> wrote: > >> >>It's an interesting idea . . . I know why perforce works this way, but >>I'm curious what problem this addresses. Most of the stuff that lives >>in the P4CONFIG file is located in <project>/settings.py, as far as I >>can tell. And I'm not clear how this would solve the problem of Python >>knowing where to look for your project files in the first place. > > > > I guess I wasn't clear. What p4 does (and I propose django-admin does) is > look for an environment variable called DJANGO_SETTINGS_NAME, and use " > settings.py" if it doesn't find such an environment variable. It then looks > for a file with that name in the CWD. If it doesn't find one there, it looks > in parent directories, until it finds one. That's the settings file that is > used. > > This would allow one to switch projects just by changing directories, and > change from dev to production by changing an env't variable (across all > projects). > > Hope that's clearer. > > --david >
I think that sounds pretty good.
