Python
/
uv
mirror of https://github.com/astral-sh/uv
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document bytecode compilation in pip compatibility guide (#4195) 

## Summary

Closes #4188.
This commit is contained in:
Charlie Marsh 2024-06-10 05:58:08 -07:00 committed by GitHub
parent 72bc739a64
commit 163f328aea
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
PIP_COMPATIBILITY.md
View File

@ -310,6 +310,12 @@ the package is "allowed" in such cases without building its metadata.
Both pip and uv allow editables requirements to be built and installed even when `--only-binary` is Both pip and uv allow editables requirements to be built and installed even when `--only-binary` is
provided. For example, `uv pip install -e . --only-binary :all:` is allowed. provided. For example, `uv pip install -e . --only-binary :all:` is allowed.
## Bytecode compilation
Unlike pip, uv does not compile `.py` files to `.pyc` files during installation by default (i.e.,
uv does not create or populate `__pycache__` directories). To enable bytecode compilation
during installs, pass the `--compile-bytecode` flag to `uv pip install` or `uv pip sync`.
## Strictness and spec enforcement ## Strictness and spec enforcement
uv tends to be stricter than `pip`, and will often reject packages that `pip` would install. uv tends to be stricter than `pip`, and will often reject packages that `pip` would install.