I need to install psycopg2 v2.4.1 specifically. I accidentally did:
pip install psycopg2
pip install psycopg2==2.4.1
That installs 2.4.4 instead of the earlier version.
Now even after I pip uninstall psycopg2 and attempt to reinstall with the correct version, it appears that pip is re-using the cache it downloaded the first time.
How can I force pip to clear out its download cache and use the specific version I’m including in the command?
If using pip 6.0 or newer, try adding the
If using pip older than pip 6.0, upgrade it with
pip install -U pip.
Clear the cache directory where appropriate for your system
Linux and Unix
~/.cache/pip # and it respects the XDG_CACHE_HOME directory.
20.1 or later, you can find the full path for your operating system easily by typing this in the command line:
pip cache dir
Example output on my Ubuntu installation:
? pip3 cache dir /home/tawanda/.cache/pip
From documentation at https://pip.pypa.io/en/latest/reference/pip_install.html#caching:
Starting with v6.0, pip provides an on-by-default cache which
functions similarly to that of a web browser. While the cache is on by
default and is designed do the right thing by default you can disable
the cache and always access PyPI by utilizing the
(pip maintainer here!)
The specific issue of “installing the wrong version due to caching” issue mentioned in the question was fixed in pip 1.4 (back in 2013!):
Fix a number of issues related to cleaning up and not reusing build directories. (#413, #709, #634, #602, #939, #865, #948)
Since pip 6.0 (back in 2014!),
pip download and
pip wheel commands can be told to avoid using the cache with the
--no-cache-dir option. (eg:
pip install --no-cache-dir <package>)
Since pip 10.0 (back in 2018!), a
pip config command was added, which can be used to configure pip to always ignore the cache —
pip config set global.cache-dir false configures pip to not use the cache “globally” (i.e. in all commands).
Since pip 20.1, pip has a
pip cache command to manage the contents of pip’s cache.
pip cache purgeremoves all the wheel files in the cache.
pip cache remove matplotlibselectively removes files related to a matplotlib from the cache.
In summary, pip provides a lot of ways to tweak how it uses the cache:
pip install --no-cache-dir <package>: install a package without using the cache, for just this run.
pip config set global.cache-dir false: configure pip to not use the cache “globally” (in all commands)
pip cache remove matplotlib: removes all wheel files related to matplotlib from pip’s cache.
pip cache purge: to clear all files from pip’s cache.
pip can install a package ignoring the cache, like this
pip --no-cache-dir install scipy
On Ubuntu, I had to delete
Since pip 20.1b1, which was released on 21 April 2020 and “added
pip cache command for inspecting/managing pip’s wheel cache”, it is possible to issue this command:
pip cache purge
The reference guide is here:
The corresponding pull request is here.
If you like to set the
--no-cache-dir option by default, you can put this into pip.conf:
[global] no-cache-dir = false
Note 1: It’s confusing, but to enable the
no-cache-dir option you actually have to set it to
false. Pretty silly if you ask me… but that’s how it is. There is a github issue to fix this.
Note 2: The location of
pip.conf depends on your OS. See the documentation for more info.
I just had a similar problem and found that the only way to get pip to upgrade the package was to delete the
%CD%build on Windows) directory that might have been left over from a previously unfinished install or a previous version of pip (it now deletes the build directories after a successful install).
On archlinux pip cache is located at ~/.cache/pip, I could solve my issue by removing the http folder inside it.
On my mac I had to remove the cache directory
On Windows 7, I had to delete
If using virtualenv, look for the
build directory under your environments root.
I had to delete %TEMP%pip-build On Windows 7
On Mac OS (Mavericks), I had to delete
A better way to do it is to delete the cache and rebuild it. In this way, if you install it again for other virtualenv, it will use the cache instead of building every time when you install it.
For example, when you install it, it will say it uses cached wheel,
Just delete that one and restart your install.
rm -d -r "$(pip cache dir)"
(…) it appears that pip is re-using the cache (…)
I’m pretty sure that’s not what’s happening. Pip used to (wrongly) reuse build directory not cache. This was fixed in version 1.4 of pip which was released on 2013-07-23.