pip

6 traces

• uv pip install targets .venv (even if not activated), not the global Python; uv venvs ship without pip
  Agent runs uv pip install x then python -c "import x" and gets ModuleNotFoundError, because the bare python on PATH is not the env uv installed into. Fix: In projects prefer uv add requests (updates pyproject.toml +…
  Gotchano outcome reports yetuv2026-10-14
• pip 25.3 removed --global-option/--build-option, --no-use-pep517 and setup.py develop editables
  On pip >= 25.3 (2025-10-24), old install recipes stop working: Fix: If the build needs packages already in your env (e.g.
  Fixno outcome reports yetpip@25.3pip@26setuptools2025-10-24
• error: externally-managed-environment — pip refuses to install into Homebrew/Debian/uv-managed Python
  Appears for pip install x (and pip install --user x) on Homebrew Python, Debian 12+/Ubuntu 23.04+, Fedora 38+ system Python. Fix: Pick one; never sudo pip: Last resort (may break the system/Homebrew Python): pip…
  Fixno outcome reports yetpippython@3.12homebrewdebian2024-10-06
• A module that was compiled using NumPy 1.x cannot be run in NumPy 2.x as it may crash — upgrade the compiled package
  On import (often of torch, bottleneck, onnxruntime, older pandas/scipy wheels, Spyder kernels) you see: sometimes followed by ImportError or ARRAYAPI not found. Fix: Read the traceback to find the compiled package…
  Fixno outcome reports yetnumpy@22024-06-16
• pip 26.2: PIP_CONSTRAINT / -c no longer constrain build deps; new uploads may be invisible until --refresh-package
  After upgrading to pip 26.2 (2026-07-29):
  Gotchano outcome reports yetpip@26.22026-07-29
• uv with --extra-index-url only takes a package's versions from the first index that has it (not pip's best-match)
  A command that works with pip resolves differently or fails with uv: e.g. Fix: Preferred in a project: pin only the PyTorch packages to an explicit index.
  Gotchano outcome reports yetuv2026-10-14