-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Hanne,

On 10/11/2011 06:31 AM, Hanne Moa wrote:
> I already do it this way except the manage.py is vanilla.
> 
> project-package/
>     project.wsgi
>     requirements.txt
>     setup.py
>     .git
>     bin/   # virtualenv
>     ...
>     project/
>         __init__.py
>         manage.py
>         settings.py
>         urls.py
>         ...

I think many people are doing something similar to this - just taking
the current startproject layout and wrapping it in an outer container
directory. This solves problems 3 and (partly) 4, out of the five I
listed. It means renaming the outermost directory no longer causes
issues (#3), and it means that although you could have something
adjacent to "project/" accidentally imported without seeming to be on
sys.path, at least it'd be reliably reproduced because its a part of
your repo, not outside it (thus partly #4).

It doesn't do anything to solve 1, 2, or 5, because you still have the
sys.path hack in setup_environ and you still have the doubled import
paths, where you can import both "project.settings" and just "settings".

Carl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6UY+AACgkQ8W4rlRKtE2f9bACfT5GLcOtz0RGWtMHhZYD0j2Zi
zJwAn1z8qfxw3m6JXEPtwbQL+6JPnSzr
=lnk9
-----END PGP SIGNATURE-----

-- 
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.

Reply via email to