From 2c1711b201bb9892211d323f2bf2a526f3e2c6d5 Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Sun, 19 May 2024 20:59:15 -0400 Subject: [PATCH] Explicitly mention --user in compatibility guide --- PIP_COMPATIBILITY.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/PIP_COMPATIBILITY.md b/PIP_COMPATIBILITY.md index 3c1db903c329..4390d0fdcfba 100644 --- a/PIP_COMPATIBILITY.md +++ b/PIP_COMPATIBILITY.md @@ -282,6 +282,17 @@ In some cases, `uv pip check` will surface diagnostics that `pip check` does not For example, unlike `uv pip check`, `pip check` will _not_ warn when multiple versions of a package are installed in the current environment. +## `--user` and the `user` install scheme + +uv does not support the `--user` flag, which installs packages based on the `user` install scheme. +Instead, we recommend the use of virtual environments to isolate package installations. + +Additionally, pip will fall back to the `user` install scheme if it detects that the user does not +have write permissions to the target directory, as is the case on some systems when installing into +the system Python. uv does not implement any such fallback. + +For more, see [#2077](https://github.com/astral-sh/uv/issues/2077). + ## Strictness and spec enforcement uv tends to be stricter than `pip`, and will often reject packages that `pip` would install.