OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
pacman-aur low very-common DISPUTE

Install Python packages despite 'error: externally-managed-environment'

archomarchyendeavouroscachyosmanjaropythondesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The cause holds. Confirmed locally: /usr/lib/python3.14/EXTERNALLY-MANAGED is owned by python 3.14.7-1, and its text matches the symptom and names python -m venv and python-pipx. Forum thread 286788 shows the same error, and the Arch wiki Python page describes the PEP 668 marking and lists pipx and uv. python-pipx (1.15.0) and uv (0.12.23) are both in extra per archlinux.org. omarchy install dev-env python exists, runs mise use --global python@latest and installs uv from astral.sh. One claim is fabricated precision: 'uv ... (Omarchy 4 has it installed)'. uv is in no *.packages file in /usr/share/omarchy/install or in the quattro tree. On this workstation /var/log/pacman.log shows it arriving after the Omarchy install, in a manual pacman -S ... protontricks gamemode ... uv. A stock Omarchy 4 has no uv, so uv tool install fails with command not found. The fix is corrected to install it first.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

pip install --break-system-packages (or deleting EXTERNALLY-MANAGED) can overwrite modules that pacman-installed tools depend on and break them, and pacman will later report file conflicts in /usr/lib/python3.x.

Symptom

pip install stopped working, with or without --user or sudo:


$ pip install requests
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try 'pacman -S
    python-xyz', where xyz is the package you are trying to
    install.

Cause

Arch's python package ships the marker file /usr/lib/python3.14/EXTERNALLY-MANAGED (the version in the path follows the installed python), as defined by PEP 668. pip refuses to install into an interpreter carrying it, including into ~/.local, because modules installed there land on the system Python's import path and can break pacman-installed Python tools. This is upstream pip behaviour that Arch enabled, not a fault on your system.

Fix

Pick by what you are installing.

**A library or tool Arch packages.** Install it with pacman:


pacman -Ss '^python-requests$'
sudo pacman -S python-requests

**A command-line application from PyPI.** Install it in its own environment. uv and pipx are both in the Arch repositories. Neither is installed by default on Omarchy 4, so install one first:


sudo pacman -S uv && uv tool install httpie
# or
sudo pacman -S python-pipx && pipx install httpie

**Dependencies for a project.** Use a virtual environment:


python -m venv .venv
.venv/bin/pip install -r requirements.txt

**Omarchy 4.** omarchy install dev-env python installs a separate Python with mise, plus uv from astral.sh into your home directory, intended for development work. Use that for projects and keep /usr/bin/python for system tools.

Avoid --break-system-packages.

Verify

The tool runs from its environment (uv tool list or pipx list shows it, or .venv/bin/python -c 'import requests' succeeds), and pacman -Qkk python reports no altered files.

Sources

pip-externally-managed-environment