I recently ran into an issue when using pip
's -I
flag that I wanted to document somewhere:
-I
will not uninstall the existing package before proceeding; it will just install it on top of the old one. This means that any files that should be deleted between versions will instead be left in place. This can cause weird behavior if those files share names with other installed modules.
For example, let's say there's a package named package
. In one of package
s files, they use import datetime
. Now, in [email protected]
, this points to the standard library datetime
module, but in [email protected]
, they added a local datetime.py
as a replacement for the standard library version (for whatever reason).
Now lets say I run pip install package==3.0.0
, but then later realize that I actually wanted version 2.0.0
. If I now run pip install -I package==2.0.0
, the old datetime.py
file will not be removed, so any calls to import datetime
will import the wrong module.
In my case, this manifested with strange syntax errors because the newer version of the package added a file that was only compatible with Python 3, and when I downgraded package versions to support Python 2, I continued importing the Python-3-only module.
Based on this, I would argue that uninstalling the old package is always preferable to using -I
when updating installed package versions.