Use back up versions in case pip-compile fails to do dependency resolution #394
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.
This is a fix for the following issue #366 where two level dependencies in turn have a single dependency that are pinned to different versions respectively. In such a case the following error happens.
In the above example I might only care about
coverage==3.6
and not care about other versions. But right now in the above scenariopip-compile
just quits on us.In such a case, this pr gives the option to provide an optional parameter to a file containing json data that has backup versions of your required dependencies, in case pip-compile faces the above error.
For e.g in this case a
backup_versions.txt
could simply be a file containing a json below.Then you would just provide the path of the backup file when doing pip-compile
pip-compile -vv requirements.in --backup-versions backup_versions.txt