Skip to content

Commit

Permalink
Document bytecode compilation in pip compatibility guide (astral-sh#4195
Browse files Browse the repository at this point in the history
)

## Summary

Closes astral-sh#4188.
  • Loading branch information
charliermarsh authored Jun 10, 2024
1 parent 72bc739 commit 163f328
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions PIP_COMPATIBILITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
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

uv tends to be stricter than `pip`, and will often reject packages that `pip` would install.
Expand Down

0 comments on commit 163f328

Please sign in to comment.