We could definately have it do the check pretty easily just by shoe horning some stuff at the top of setup.py, actually offering to uninstall might be more complicated, although it could probably be done in the same way.
On Sep 16, 1:20 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > We've had at least three people run into a problem (#9090) after installing > 1.0 over an old level. Now, we do document that before installing you > should remove any old level. But I find the results when you don't rather > odd. It's not just old files renamed/deleted in the new level that wind up > being 'leftover' in the site-packages directory. Rather, some files that > exist in both levels, and changed between the two, are not updated by > install. So you wind up with a mixture of 0.96.x and 1.0 level files, which > is pretty confusing and subject to odd failures. > > Does anyone know if there is something we could do to prevent this > situation? I'm not very familiar with Python installation procedures. It > seems like it would be better, though, if our installer flat-out refused to > install over a pre-existing installation or offered to delete the > pre-existing install before continuing with the new install. What's the > norm for Python packages? > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
