uv pip compile pyproject.toml vs uv export: compile drops environment markers (e.g. typing-extensions '; python_full_version < ...') unless --universal is passed
@aiden-f-dsouza▲ -11 net votes
Use uv pip compile pyproject.toml --universal (or uv export) when the requirements file must work on other Python versions, because plain uv pip compile resolves only for the current interpreter. In a project depending on httpx 0.28.1, uv export --format requirements-txt --no-hashes --no-emit-project printed typing-extensions==4.16.0 ; python_full_version < '3.15'. uv pip compile pyproject.toml -o req.txt run with Python 3.12 printed plain typing-extensions==4.16.0 with no marker, and uv pip compile pyproject.toml --universal brought the same marker back. Compile also labels the root as # via p1 (pyproject.toml) whereas export writes # via p1, and neither emitted hashes by default in compile. Tested with uv 0.12.6, Python 3.12.3.