Differing results based on platform pip-compile is run from

[ssbarnea]

While I do understand that different platforms may produce different results it i also impossible to run pip-compile for a specific target platform.

Even if you product officially ships on a single platform, the developers may use a plethora of variations when they propose a change, they should be able to recompile the target requirements.txt file.

For example if their dev machine is MacOS, or even a different python version that the shipped one you do end-up with a different requirements.txt file (even if sometimes only comments differ).

This does not play well at all with CI usage, where you likely have one job that recompiles requirements.in and fails the build if the produced file is different.

We clearly need a reproducible way to recompile requirements that does not force PR creator to execute pip-compile on a very particular platform.

[stianlagstad]

Here's an issue describing the same problem with another package manager:

• Multi Platform support for Pipfile.lock pypa/pipenv#5130
• Platform sensitive lock mechanism pypa/pipenv#5561

[webknjaz]

FWIW this is explained in README already.

[doronbehar]

BTW I tried today to use the --pip-args '--platform=linux-armv7l' for this pyproject.toml, and the resulting requirements.txt file didn't include the pyrp3 dependency... I wonder why 🤔.

FWIW this is explained in README already.

What is explained?

[webknjaz]

file didn't include the pyrp3 dependency... I wonder why 🤔.

I think pip only applies this to selecting wheels. I'd recommend you to check what pip install does separately from pip-tools. I expect that it doesn't do anything, either.

What is explained?

This https://pip-tools.rtfd.io/en/stable/#cross-environment-usage-of-requirements-in-requirements-txt-and-pip-compile

[webknjaz]

Closing as duplicate of #826. No need to have multiple competing discussions of the same thing.