On Tue, Oct 11, 2011 at 6:05 AM, Carl Meyer <c...@oddbird.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > In the spirit of making Django behave better as a Python library (c.f. > Glyph's keynote at djangocon.us), I'd like to finally tackle removing > the sys.path hacks in django.core.management.setup_environ. I'll give > the full detailed rundown here on the current behavior and how I propose > to change it. Fortunately, the fix isn't that complicated, and I think > it's a no-brainer. For the impatient, you can skip straight to my > proposed patch [2]. > > The tl;dr summary is that I think with some small changes to manage.py > and the default project layout, we can fix some very common bugs and > deployment problems, dramatically reduce the extent to which manage.py > is "unknown magic" for newcomers to Django, and take a significant step > towards being "just a Python library."
Pile on another +1 from me too. This looks like an extremely elegant solution to something that has been a wart for a long time. My only feedback on the patch is a point of clarification in the tutorial. Rather than creating a mysite directory with a mysite project directory in it, and then having to refer to the "inner/outer directory" or "the directory with manage.py in it", it strikes me that it might be cleaner to name the outer directory something generic (like "django_tutorial"). This reinforces that the outer directory name doesn't matter, and that startproject is only creating the inner directory. Other than that, it looks great to me. Russ %-) -- 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.
