Use PIPENV_SKIP_LOCK environment variable #4797
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.
The issue
The value of
PIPENV_SKIP_LOCK
is always False. This has been discussed in previous issues (#2200 and #3332) with no resolution.The fix
PIPENV_SKIP_LOCK
to consider the value of the environment variablePIPENV_SKIP_LOCK
.This is useful to large project as it enables the environment variable
PIPENV_SKIP_LOCK
to control the locking behavior.Default behavior is not changed, still False.
The checklist
news/
directory to describe this fix with the extension.bugfix
,.feature
,.behavior
,.doc
..vendor
. or.trivial
(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.