How to remove a Python package

Removing one Python package is useful when a dependency is no longer needed, conflicts with an application, or needs a clean reinstall without rebuilding the whole environment. A targeted uninstall keeps the change small and makes it easier to confirm exactly which interpreter or virtual environment lost the package.

The supported workflow is to run pip uninstall through the exact interpreter that owns the package, usually as python3 -m pip uninstall on POSIX shells or py -m pip uninstall on Windows. pip removes files recorded for the installed distribution package in that environment, so checking the active interpreter and the package metadata first prevents removing the wrong copy on hosts that carry multiple Python installs.

Removal only affects the current environment. Homebrew, apt, dnf, and other distributors can mark system interpreters as externally managed, so globally managed packages usually belong to the platform package manager instead, and legacy python setup.py install or python setup.py develop installs may not uninstall cleanly because pip does not always have complete file metadata for them.

1. Confirm which interpreter and pip installation will lose the package.

   $ python3 -m pip --version
   pip 26.0.1 from /srv/apps/example-inventory/.venv/lib/python3.14/site-packages/pip (python 3.14)

   The path after from identifies the virtual environment or interpreter that the uninstall command will modify.

   Use py -m pip --version on Windows when the launcher is the normal entry point.

   Related: How to activate a Python virtual environment

2. Inspect the installed distribution metadata before removing anything.

   $ python3 -m pip show example-inventory-client
   Name: example-inventory-client
   Version: 2.4.1
   Summary: Python client for the Example inventory API.
   Home-page: https://packages.example.test/example-inventory-client
   Author: Example Platform Team
   Author-email: packages@example.test
   License: MIT
   Location: /srv/apps/example-inventory/.venv/lib/python3.14/site-packages
   Requires: httpx, pydantic
   Required-by:

   The Required-by field is the fastest warning that another installed package still depends on the target package.

   Related: How to show installed Python package information

3. Remove the package from the same interpreter or virtual environment.

   $ python3 -m pip uninstall example-inventory-client
   Found existing installation: example-inventory-client 2.4.1
   Uninstalling example-inventory-client-2.4.1:
     Would remove:
       /srv/apps/example-inventory/.venv/lib/python3.14/site-packages/example_inventory_client-2.4.1.dist-info/*
       /srv/apps/example-inventory/.venv/lib/python3.14/site-packages/example_inventory_client/*
   Proceed (Y/n)? y
     Successfully uninstalled example-inventory-client-2.4.1

   Use -y to skip the confirmation prompt in automation or other non-interactive shells.

   If pip uninstall returns error: externally-managed-environment, switch to a project virtual environment or remove the distro-managed package with apt, dnf, brew, or the platform package manager instead of forcing the change into a system interpreter.

4. Confirm that pip no longer reports the package in the same environment.

   $ python3 -m pip show example-inventory-client
   WARNING: Package(s) not found: example-inventory-client

   This warning is the expected result after a successful uninstall from the current interpreter.

5. Check the remaining environment for dependency breakage after the removal.

   $ python3 -m pip check
   No broken requirements found.

   If pip check reports a missing or incompatible dependency, restore the package or reinstall the project's tested dependency set before continuing.

   Related: How to install Python packages from a requirements file