Moving the manage.py is a great move. Post 1.4 you actually might want to think a bit about integrating a distutils2 setup.cfg into the manage.py folder and the startproject command.
Since distutils2 will be the standard in python3.3 for packaging and backported to python 2.5 it makes sense to leverage it for Django. At the very least the setup.cfg could provide the DJANGO_SETTINGS_MODULE env variable for installation scripts as a custom meta-data variable that an installation script could do something with. It will probably be good practice to setup a minimal setup.cfg file anyway with the project name. My thoughts are that the whole Django project structure existed as a way to get started quickly, and people replicated it on servers because python packaging sucked. Hopefully distutils2 will make it suck a little less and make it feasible to make Django play nicely with it. Brett H -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
