Do not add --upgrade flag to generated output file

[hofrob]

uv and pip-tools both add the full command to the generated output file. When running an upgrade command, uv will add --upgrade too while pip-tools will not.

This flag in particular should be ignored when generating the output file I think. My reasoning is, I'm running pre-commit checks that will only check if the generated file from pyproject.toml is consistent with the requirements.txt in the repo. Since the command does not use --upgrade it will detect a change in the generated output after an upgrade.

Or if I do not execute my hooks, the CI will complain because the files were changed by doing uv pip compile.

pip-tools

pip-compile --upgrade
pip-compile

Both commands will generate the same output file.

uv

uv pip compile pyproject.toml --upgrade --output-file requirements.txt
uv pip compile pyproject.toml --output-file requirements.txt

The generated outputs will be different: the first one will contain the --upgrade flag, the second one won't.

[hofrob]

Another one that's ignored by pip-tools: --quiet

Additionally, this is nothing too serious, but I thought I'd mention it: From what I've seen pip-tools also re-orders the CLI args before creating the output file. So when changing order of the CLI params in our scripts, the generated file is still the same.

I tested this by running pip-compile --strip-extras --quiet --extra-index-url=https://pypi.example.net/.... The command in the requirements.txt will look like this: pip-compile --extra-index-url=https://pypi.example.net/... --strip-extras

[charliermarsh]

Agreed.