Never really understood why you needed this in the first place. The automatic setuptools installation has caused me some grief as it installs an obsolete version ... I forgot the exact specifics but it took me quite a while to track down that installing django was causing all kinds of strange problems with other python modules.
I think it is fair to say that having the situation where installing django will also covertly install setuptools is greatly undesirable. As many have pointed out, using a MANIFEST.in provides a very simple means to use file globbing for files and directories. If that was the main reason for using setuptools you'd have a straightforward solution right away. i. ps. Nowadays I don't ever install it, I just simply add the django folder to my python path and have not had any problems. I would not treat django as a python module anymore, installing into the python site libraries makes keeping track of different releases very difficult. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
