[marclave]

> Like pip-compile, uv generates a platform-specific requirements.txt file (unlike, e.g., poetry and pdm, which generate platform-agnostic poetry.lock and pdm.lock files). As such, uv's requirements.txt files may not be portable across platforms and Python versions.

really curious on the reasoning behind this decision :)

[Too]

Hard to give a concrete example but you can end up in dependency deadlocks, with combination of packages that require new features vs packages that don’t work on newer versions.

Mostly it’s useful right after a new release where prebuilt wheels aren’t available for all packages yet and you have users who may care or not about this.

If you only have single requirements file, you get forced to choose which platform to support. With multiple, you can break out if needed. These breaking changes and deadlocks are rare. It’s still good to have an escape hatch.

[anentropic]

https://github.com/astral-sh/uv?tab=readme-ov-file#multi-ver...

says:

> uv does not yet produce a machine-agnostic lockfile.

so maybe the non-portable requirements.txt is just a first milestone