ChatGPT解决这个技术问题 Extra ChatGPT

What is the easiest way to remove all packages installed by pip?

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?

@patelshahrukh uninstalling python DOES NOT remove pip packages. please AVOID doing that, since it both most likely WON'T WORK the way you think it will, and, depending on how you install python again, can leave your machine in an unstable state that's more work to fix.
this might help for packages installed in development mode or editable mode: stackoverflow.com/questions/17346619/…

b
blueberryfields

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 -y

In 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

I find this a good solution, purely because it doesn't remove the virtual environment entirely - I may have made changes to e.g. postactivate which will remain.
After running this I realized it removed the setuptools package. I resolved the issue following instructions here: stackoverflow.com/questions/7446187/…
You can also use pip freeze --exclude-editable | xargs pip uninstall -y to ignore VCS packages without using a grep pattern
ERROR: Invalid requirement: '@' I have packages that ive installed from my gitlab.
pip freeze lists all packages, including those installed in the OS. User will is unable (and possibly does not want) to remove them without root permissions. pip freeze --user worked for me.
H
Harshad Kavathiya

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.txt

Now to remove one by one

pip uninstall -r requirements.txt

If we want to remove all at once then

pip uninstall -r requirements.txt -y

If 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)

probably worth mentioning that you are force overwriting their requirements.txt file, in case they didn't know. :)
In addition, if one wants to remove all packages, appending "-y" will do so. Example: pip uninstall -r requirements.txt -y
You can use pip uninstall -y -r <(pip freeze) to do everything in one go.
@joeb yes we can do that way also.
@HarshadKavathiya you can use another file to store pip freeze, like "current.txt", so requirements.txt can stay untouched cheers
R
Robert Moskal

This works with the latest. I think it's the shortest and most declarative way to do it.

virtualenv --clear MYENV

But 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.


Is this effectively the same as running wipeenv? virtualenvwrapper.readthedocs.org/en/latest/…
Actually — it seems (from what I just ran into) whereas wipeenv while within the environment throws an error and doesn't remove anything if used in the context of a pip install -e development build, attempting to use virtualenv --clear MYENV doesn't throw an error and removes none of the packages that you may have installed previously in the environment. At least this is the case on OSX. See bitbucket.org/dhellmann/virtualenvwrapper/issues/211/… for further info.
wipeenv is an alias provided by virtualenvwrapper, so not everyone has it.
well, this is kind of a dirty trick, but works like magic. I would prefer that everyone to use pip uninstall -r requirements.txt -y. It makes a great clean up.
T
Taylor D. Edmiston

I 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:

pipuninstallall

Alternative for Pipenv

If you are using pipenv, you can run:

pipenv uninstall --all

Alternative 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.)


I like it but it doesn't work in the null case (pip freeze results in nothing output if no packages installed, and then pip uninstall complains, unfortunately).
Hmm good catch. Perhaps it could be wrapped into a bash function that checks whether the pip freeze output is non-empty. I don't see a great way to achieve that while keeping the command a nice short one-liner.
make uses sh by default, but the substitution syntax <(...) is a bashism. So you can either use bash -c "...", or work around by doing a pip freeze | pip uninstall -r /dev/stdin
Does not work with Azure Notebooks: ERROR: Cannot uninstall 'bitarray'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
@SeaDude Here is a workaround that may help - stackoverflow.com/questions/49915951/cannot-uninstall-chardet. If that doesn't work, then this approach would be my next best guess - github.com/vlachoudis/bCNC/issues/1141. Note that the packages mentioned are different, but I believe the underlying issue may be similar.
n
nehem

Other 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 -y

Ref: pip freeze --help


This worked until it hit a package that produced this error: ERROR: Cannot uninstall 'bitarray'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.. Then I couldn't uninstall any more modules.
K
K-Dawg

I managed it by doing the following:

Create the requirements file called reqs.txt with 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.txt

I 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).


S
Sathiamoorthy

Best way to remove all packages from the virtual environment:

Windows:

pip freeze > unins && pip uninstall -y -r unins && del unins

Linux:

pip3 freeze > unins && pip3 uninstall -y -r unins && rm unins

If not work, change && to ; in the above commands.


Windows: no such option: -y
@variable, for me windows command is working
b
blueberryfields

Method 1 (with pip freeze)

pip freeze | xargs pip uninstall -y

Method 2 (with pip list)

pip list | awk '{print $1}' | xargs pip uninstall -y

Method 3 (with virtualenv)

virtualenv --clear MYENV

sudo is not necessary, and quite probably dangerous to use without careful consideration, since it affects the global machine setup. see this answer for example: stackoverflow.com/questions/15028648/…
Method 2 (pip list) works great until you have pip accidentally uninstall itself -_-
Method 2 didn't work in my case because there is a header in the list which needs to be ignored. This one worked: pip list | awk '{print $1}' | grep -vE "^pip$|^Package$|^---" | xargs pip uninstall -y
R
Richard Kenneth Niescior

On Windows if your path is configured correctly, you can use:

pip freeze > unins && pip uninstall -y -r unins && del unins

It should be a similar case for Unix-like systems:

pip freeze > unins && pip uninstall -y -r unins && rm unins

Just 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.


K
Kalanos

I use the --user option to uninstall all the packages installed in the user site.

pip3 freeze --user | xargs pip3 uninstall -y

I believe this answer doesn't add much new information, I would rather have suggested an improvement to another already existing similar answer such as this one: stackoverflow.com/a/45475070/11138259
If you are using a virtualenv and get ERROR: You must give at least one requirement to uninstall, remove the --user part
pip3 freeze | xargs pip3 uninstall -y ==> ` PermissionError: [Errno 13] Permission denied: '/usr/local/bin/ap' -> '/tmp/pip-uninstall-q9gzbj0d/ap'`
@SL5net. You might need to run it as superuser. Something like sudo sh -c 'pip3 freeze | xargs pip3 uninstall -y' (The added sh -c and quotes are because pipe doesnt tend to play nicely with sudo) Or you could just do your command as root, but I dont recomend that as its not a great habit to be in. shelling about in root makes it pretty easy to accidently murder your system, trust me, bitter experience talking here.
s
shafik

First, add all package to requirements.txt

pip freeze > requirements.txt

Then remove all

pip uninstall -y -r requirements.txt 

d
dwlz

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

Does this even handle the case where there was a editable install (basically a setuptools develop mode install) that created a local .egg-info file that then interfered with the rest of the installation/uninstallation process? Since it's a set of files it doesn't seem to know how to handle their presence, and rather than uninstalling anything it makes a local directory structure under MYENV complete with: ` > New python executables in MYENV/bin/python3.4 > Also creating executable in MYENV/bin/python > Installing setuptools, pip, wheel...done.` But MYENV hasn't reset the environment!
b
benwrk

For Windows users, this is what I use on Windows PowerShell

 pip uninstall -y (pip freeze)

G
GabLeRoux

Using virtualenvwrapper function:

wipeenv

See wipeenv documentation


If you are using virtualenvwrapper, type wipeenv
C
Craicerjack

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


T
Thibaut Dubernet

(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 -y

from 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.


o
obotezat
pip3 freeze --local | xargs pip3 uninstall -y

The case might be that one has to run this command several times to get an empty pip3 freeze --local.


H
Huey

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))

M
Mahdi Hamzeh

the easy robust way cross-platform and work in pipenv as well is:

pip freeze 
pip uninstall -r requirement

by pipenv:

pipenv run pip freeze 
pipenv run pip uninstall -r requirement

but won't update piplock or pipfile so be aware


S
Samuel Marks

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.

B
Brian Tompsett - 汤莱恩

On Windows if your path is configured correctly, you can use:

pip freeze > unins && pip uninstall -y -r unins && del unins

S
SohailAQ

This works on my windows system

pip freeze > packages.txt && pip uninstall -y -r packages.txt && del packages.txt

The 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.


F
Fei Xie

This is the command that works for me:

pip list | awk '{print $1}' | xargs pip uninstall -y

p
punkrockpolly

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/projectx

if 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


S
Sushant Chaudhary

In Command Shell of Windows, the command pip freeze | xargs pip uninstall -y won'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 freeze command to a .txt file. Then, go the location of your .txt file and run the command pip uninstall -r *textfile.txt*


M
Mohammad Banisaeid

If you are using pew, you can use the wipeenv command:

pew wipeenv [env]


v
verboze

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.


e
erfoon maraghi

Select Libraries To Delete From This Folder:

C:\Users\User\AppData\Local\Programs\Python\Python310\Lib\site-packages


Although this does delete all packages (and more), it doesn't do so with pip as the question asked.
R
Radon Rosborough

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 python

Or, if you were using pip3:

$ brew reinstall python3

This answer assumes too much about the environment and doesn't directly solve the problem if you are using pyenv for example.
@Mark Well sure if you're using pyenv, then you would need to do something different. In the common case that you're not, I believe this is the simplest and least hacky solution. Note that this condition is explicitly stated at the beginning of the answer.
The OP asked about virtualenvs. He made no specific mention of using a Mac or brew to install Python. Therefore you cannot assume the OS or brew was used - and this answer will not solve ALL conditions. If you focus on solving for the environment using a tool such as pip - you will address the context of the environment you are within. Hope that makes sense.
@Mark I understand your position. We can agree to disagree. I just want to help out the people from Google who click on a link labelled "What is the easiest way to remove all packages installed by pip?" when they really want to remove all packages installed globally by pip.
Agreed with @RadonRosborough, the link title is representative of why I landed here, even if the OP does not actually ask the same question.
g
glenda

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 -fr

for 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 -fr

then to clean up empty directories left over:

find /usr/lib/python2.7 -type d -empty |xargs rm -fr

I 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.


With all due respect, this seems comparable. Why not dpkg-query -S '/usr/lib/python2.7/*', extract the names, and dpkg-query -L each name to dump the associated files? It already has the manifests prepared. My main objection is that instead of targeting packages installed anywhere but by pip, you've targeted packages installed by anything other than the manager you expect, and in a location that pip generally shouldn't be touching. pip list -l lists the packages it installed locally, and some will even pip install --target=.... Removing all currently empty dirs will bite you too!