2011/10/11 Carl Meyer <c...@oddbird.net>: > Unless there are significant objections, I'd like to commit this in the > next few days and get it into 1.4. I'll also modify the patch on #16360 > to take advantage of the new layout; hopefully that can get into 1.4 as > well. > > Let me know if you see something I've overlooked!
Carl, +1 from me too. The new structure highlights that a Django project is: - an entrypoint for scripts manage.py — and soon another one for WSGI servers, - a settings module and a root URLconf, who happen to live in the same package by default, - some applications, templates, static files, etc. I was about to ask a question about the recommended project layout but I eventually found the answer here: https://github.com/carljm/django/commit/4ba999060d8c030dd43ef4a8ec2844850f0310b3#L2R380 This information will still be interesting and useful long after the 1.4 release. Shouldn't we move it somewhere in the documentation and link to that page from the release notes? Also, following the Zen of Python, shouldn't we recommend the decoupled style (ie. put apps in the outer "mysite" directory)? Finally, if I understand correctly, the only reason why the default settings and URLconf are in a package ("mysite.settings" and "mysite.urls") is to avoid name conflicts. In particular, it makes it possible to run several Django projects in parallel with the same PYTHONPATH. It'd be worth mentioning this in the documentation, so that newcomers understand there's nothing magic with the name of the inner "mysite" directory. I believe all this could go either in the tutorial or in a new page dedicated to project layout — the latter would allow us to give more details on the project layout options. Thanks for your work on this long-standing issue! -- Aymeric. -- 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.