I'm trying to fix up one of my virtualenvs - I'd like to reset all of the installed libraries back to the ones that match production.
Is there a quick and easy way to do this with pip?
230 Answers
I've found this snippet as an alternative solution. It's a more graceful removal of libraries than remaking the virtualenv:
pip freeze | xargs pip uninstall -yIn case you have packages installed via VCS, you need to exclude those lines and remove the packages manually (elevated from the comments below):
pip freeze | grep -v "^-e" | xargs pip uninstall -y 23 This will work for all Mac, Windows, and Linux systems. To get the list of all pip packages in the requirements.txt file (Note: This will overwrite requirements.txt if exist else will create the new one, also if you don't want to replace old requirements.txt then give different file name in the all following command in place requirements.txt).
pip freeze > requirements.txtNow to remove one by one
pip uninstall -r requirements.txtIf we want to remove all at once then
pip uninstall -r requirements.txt -yIf you're working on an existing project that has a requirements.txt file and your environment has diverged, simply replace requirements.txt from the above examples with toberemoved.txt. Then, once you have gone through the steps above, you can use the requirements.txt to update your now clean environment.
And For single command without creating any file (As @joeb suggested).
pip uninstall -y -r <(pip freeze) 13 This works with the latest. I think it's the shortest and most declarative way to do it.
virtualenv --clear MYENVBut why not just delete and recreate the virtualenv?
Immutability rules. Besides it's hard to remember all those piping and grepping the other solutions use.
4I wanted to elevate this answer out of a comment section because it's one of the most elegant solutions in the thread. Full credit for this answer goes to @joeb.
pip uninstall -y -r <(pip freeze)This worked great for me for the use case of clearing my user packages folder outside the context of a virtualenv which many of the above answers don't handle.
Edit: Anyone know how to make this command work in a Makefile?
Bonus: A bash alias
I add this to my bash profile for convenience:
alias pipuninstallall="pip uninstall -y -r <(pip freeze)"Then run:
pipuninstallallAlternative for Pipenv
If you are using pipenv, you can run:
pipenv uninstall --allAlternative for Poetry
If you are using Poetry, run:
poetry env remove --python3.9(Note that you need to change the version number there to match whatever your Python version is.)
5Other answers that use pip list or pip freeze must include --local else it will also uninstall packages that are found in the common namespaces.
So here are the snippet I regularly use
pip freeze --local | xargs pip uninstall -yRef: pip freeze --help
I managed it by doing the following:
- Create the requirements file called
reqs.txtwith currently installed packages list
pip freeze > reqs.txt- Then uninstall all the packages from
reqs.txt
# -y means remove the package without prompting for confirmation
pip uninstall -y -r reqs.txtI like this method as you always have a pip requirements file to fall back on should you make a mistake. It's also repeatable, and it's cross-platform (Windows, Linux, MacOs).
0Best way to remove all the packages from the virtual environment
Windows:
pip freeze > unins && pip uninstall -y -r unins && del uninsLinux:
sudo pip3 freeze > unins && pip3 uninstall -y -r unins && rm uninsIf not work, change && to ; in the above commands.
Method 1 (with pip freeze)
pip freeze | xargs pip uninstall -yMethod 2 (with pip list)
pip list | awk '{print $1}' | xargs pip uninstall -yMethod 3 (with virtualenv)
virtualenv --clear MYENV 3 On Windows if your path is configured correctly, you can use:
pip freeze > unins && pip uninstall -y -r unins && del uninsIt should be a similar case for Unix-like systems:
pip freeze > unins && pip uninstall -y -r unins && rm uninsJust a warning that this isn't completely solid as you may run into issues such as 'File not found' but it may work in some cases nonetheless
EDIT: For clarity: unins is an arbitrary file which has data written out to it when this command executes: pip freeze > unins
That file that it written in turn is then used to uninstall the aforementioned packages with implied consent/prior approval via pip uninstall -y -r unins
The file is finally deleted upon completion.
0I use the --user option to uninstall all the packages installed in the user site.
pip3 freeze --user | xargs pip3 uninstall -y 4 First, add all package to requirements.txt
pip freeze > requirements.txtThen remove all
pip uninstall -y -r requirements.txt 0 The quickest way is to remake the virtualenv completely. I'm assuming you have a requirements.txt file that matches production, if not:
# On production:
pip freeze > reqs.txt
# On your machine:
rm $VIRTUALENV_DIRECTORY
mkdir $VIRTUALENV_DIRECTORY
pip install -r reqs.txt 1 For Windows users, this is what I use on Windows PowerShell
pip uninstall -y (pip freeze) 0 Using virtualenvwrapper function:
wipeenv 1 Its an old question I know but I did stumble across it so for future reference you can now do this:
pip uninstall [options] <package> ...
pip uninstall [options] -r <requirements file> ...-r, --requirement file
Uninstall all the packages listed in the given requirements file. This option can be used multiple times.
from the pip documentation version 8.1
(adding this as an answer, because I do not have enough reputation to comment on @blueberryfields 's answer)
@blueberryfields 's answer works well, but fails if there is no package to uninstall (which can be a problem if this "uninstall all" is part of a script or makefile). This can be solved with xargs -r when using GNU's version of xargs:
pip freeze --exclude-editable | xargs -r pip uninstall -yfrom man xargs:
-r, --no-run-if-empty
If the standard input does not contain any nonblanks, do not run the command. Normally, the command is run once even if there is no input. This option is a GNU extension.
pip3 freeze --local | xargs pip3 uninstall -yThe case might be that one has to run this command several times to get an empty pip3 freeze --local.
This was the easiest way for me to uninstall all python packages.
from pip import get_installed_distributions
from os import system
for i in get_installed_distributions(): system("pip3 uninstall {} -y -q".format(i.key)) the easy robust way cross-platform and work in pipenv as well is:
pip freeze
pip uninstall -r requirementby pipenv:
pipenv run pip freeze
pipenv run pip uninstall -r requirementbut won't update piplock or pipfile so be aware
Cross-platform support by using only pip:
#!/usr/bin/env python
from sys import stderr
from pip.commands.uninstall import UninstallCommand
from pip import get_installed_distributions
pip_uninstall = UninstallCommand()
options, args = pip_uninstall.parse_args([ package.project_name for package in get_installed_distributions() if not package.location.endswith('dist-packages')
])
options.yes = True # Don't confirm before uninstall
# set `options.require_venv` to True for virtualenv restriction
try: print pip_uninstall.run(options, args)
except OSError as e: if e.errno != 13: raise e print >> stderr, "You lack permissions to uninstall this package. Perhaps run with sudo? Exiting." exit(13)
# Plenty of other exceptions can be thrown, e.g.: `InstallationError`
# handle them if you want to. On Windows if your path is configured correctly, you can use:
pip freeze > unins && pip uninstall -y -r unins && del unins This works on my windows system
pip freeze > packages.txt && pip uninstall -y -r packages.txt && del packages.txtThe first part pip freeze > packages.txt creates a text file with list of packages installed using pip along with the version number
The second part pip uninstall -y -r packages.txt deletes all the packages installed without asking for a confirmation prompt.
The third part del packages.txt deletes the just now created packages.txt.
This is the command that works for me:
pip list | awk '{print $1}' | xargs pip uninstall -y If you're running virtualenv:
virtualenv --clear </path/to/your/virtualenv>for example, if your virtualenv is /Users/you/.virtualenvs/projectx, then you'd run:
virtualenv --clear /Users/you/.virtualenvs/projectxif you don't know where your virtual env is located, you can run which python from within an activated virtual env to get the path
In Command Shell of Windows, the command
pip freeze | xargs pip uninstall -ywon't work. So for those of you using Windows, I've figured out an alternative way to do so.
- Copy all the names of the installed packages of pip from the
pip freezecommand to a .txt file. - Then, go the location of your .txt file and run the command
pip uninstall -r *textfile.txt*
If you are using pew, you can use the wipeenv command:
pew wipeenv [env]
I simply wanted to remove packages installed by the project, and not other packages I've installed (things like neovim, mypy and pudb which I use for local dev but are not included in the app requirements). So I did:
cat requirements.txt| sed 's/=.*//g' | xargs pip uninstall -y
which worked well for me.
Select Libraries To Delete From This Folder:
1C:\Users\User\AppData\Local\Programs\Python\Python310\Lib\site-packages
In my case, I had accidentally installed a number of packages globally using a Homebrew-installed pip on macOS. The easiest way to revert to the default packages was a simple:
$ brew reinstall pythonOr, if you were using pip3:
$ brew reinstall python3 5 Pip has no way of knowing what packages were installed by it and what packages were installed by your system's package manager. For this you would need to do something like this
for rpm-based distros (replace python2.7 with your python version you installed pip with):
find /usr/lib/python2.7/ |while read f; do if ! rpm -qf "$f" &> /dev/null; then echo "$f" fi
done |xargs rm -frfor a deb-based distribution:
find /usr/lib/python2.7/ |while read f; do if ! dpkg-query -S "$f" &> /dev/null; then echo "$f" fi
done |xargs rm -frthen to clean up empty directories left over:
find /usr/lib/python2.7 -type d -empty |xargs rm -frI found the top answer very misleading since it will remove all (most?) python packages from your distribution and probably leave you with a broken system.
1