This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sergio.Callegari
Recipients Sergio.Callegari, alexis, eric.araujo, illume, tarek, thomas.holmes
Date 2013-10-16.12:30:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381926621.17.0.65121953907.issue5342@psf.upfronthosting.co.za>
In-reply-to
Content
Getting bitten by this with numpy/scipy installations

Having previous scipy installed,

   pip install -I scipy

creates a broken scipy installation, because the previous one is not removed and gets overwritten. For instance, an old spectral.so file leftover hides the spectral.py file from the new installation causing broken behavior.

Similarly trying

   pip uninstall scipy
   pip install scipy

does the same, because the distutils uninstall does not uninistall anything, leaves the scipy directory there and all cheerful ends with a 'Successfully uninstalled scipy'.

This is *dangerous*. Mixing old and new code could lead to the weirdest behavior. In principle, one could even use this property to craft packages such that when two subsequent versions are installed one on top of the other malicious things happen even if individually each version is innoquous.
History
Date User Action Args
2013-10-16 12:30:21Sergio.Callegarisetrecipients: + Sergio.Callegari, illume, tarek, eric.araujo, thomas.holmes, alexis
2013-10-16 12:30:21Sergio.Callegarisetmessageid: <1381926621.17.0.65121953907.issue5342@psf.upfronthosting.co.za>
2013-10-16 12:30:21Sergio.Callegarilinkissue5342 messages
2013-10-16 12:30:20Sergio.Callegaricreate