On 08/08/2007, James Bennett <[EMAIL PROTECTED]> wrote: > > > On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote: > > I'd ideally like the Django installer to detect if django.template was > > already on the system, and drop Django into the same spot. As far as > > versioning, Django should check for a minimum version of Django > > templates (i.e., the version at the time of that Django's release), > > assuming it was already installed on the system; if it detected a > > version below the minimum, it would be nice for the installer to offer > > to simply overwrite the entire django namespace. > > In theory, setuptools can do this sort of "namespace" trick, but the > system which handles that has always seemed a little clunky to me.
My concern would be when "setup.py install" does too much clever trickery and starts conflicting with distribution packages. You install django-templates via setup.py and it ends up in /usr/local/python2.5/site-packages, then you install django & templates from your distribution and presto, your django install now pulls in templates from a different version. I know its a contrived case and there are many other opportunities for making a mess of a system, but i'd be concerned about setuptools needing to do anything but the basics. Rob :) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
