Ignore global pip config files for pip-compile #473
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
.par
files. See CONTRIBUTING.md for infoPR Type
This makes sure global pip config files don't leak into your pip-compile, similar to #389
What is the current behavior?
If a user has a global pip config file, say with extra URLs, those will get included in the output from pip-compile, but it will not be reproducible for others.
What is the new behavior?
Those files are completely ignored.
Does this PR introduce a breaking change?
If folks were relying on this, it could cause issues. This leaves the escape hatch of people being able to manually specify the
PIP_CONFIG_FILE
in theirenv
to set it explicitly.