Skip to Assistance content

Quick Answer

Separate pip upgrade problems, build failures, missing wheels, compiler errors, and Termux package dependencies before installing Python libraries.

Use this guide only when your symptom or goal matches the indicators below. If a diagnostic command reveals a different problem, follow that evidence instead of forcing every remaining step.

Last reviewed: .

Use This Guide When

Installing pip is forbiddenFailed building wheelsubprocess-exited-with-errorNo matching distribution found

Before You Run Anything

  • Copy the complete error, including the first package, file, module, or line number it names.
  • Record `termux-info`, the active language/runtime version, and the current folder before changing dependencies.
  • Do not delete package-manager locks or upgrade pip itself through pip in Termux.

Diagnostic Or Setup Commands

Termux manages pip through the `python-pip` package. Do not run `pip install --upgrade pip`; update it with `pkg upgrade python-pip`.

pkg update
pkg install -y python python-pip
python -m pip --version
python -m pip install --upgrade setuptools wheel
python -m pip install PACKAGE_NAME

What The Commands Tell You

  • `pkg update` — Refreshes the Termux package index.
  • `pkg install -y python python-pip` — Installs the listed Termux packages and dependencies.
  • `python -m pip --version` — Shows which pip belongs to the active Python.
  • `python -m pip install --upgrade setuptools wheel` — Installs or updates the named Python distribution, not pip itself.

What Success Looks Like

  • The minimal version, import, syntax, path, or package test exits successfully.
  • The original command now fails later for a different, clearly identified reason or completes normally.
  • The package manager has no interrupted configuration left pending.

Safe Next Steps

  1. Repair or update the Termux package layer before retrying a language package.
  2. Confirm that the interpreter and its package tool belong to the same installation.
  3. Install the missing system dependency before repeating a Python or Node build.
  4. Retest with a minimal version, import, compile, or file command before running the full script.

Common Mistakes

  • Using `sudo`, Ubuntu package names, or desktop paths in a normal Termux installation.
  • Assuming that a Python import name always matches the distribution name on PyPI.
  • Deleting caches, environments, or lock files before preserving the exact error and versions.

Still Stuck?

Copy the support report, fill in the missing values, and include the complete terminal output. Remove passwords, tokens, private keys, exact home paths, and personal information.

Fixed This Error But Want A Repeatable Way To Diagnose The Next One?

The Complete Termux Troubleshooting Handbook gives you a structured diagnostic process for Termux, Python, Git, storage, packages, networking and recovery instead of relying on disconnected fixes.

Preview the Handbook