setup.cfg: Relax version constraints on all dependencies#244
Merged
setup.cfg: Relax version constraints on all dependencies#244
Conversation
Collaborator
Author
|
There will be a merge conflict with #243, which should be merged first (this PR is less complex and easier to fix up) |
3 tasks
Owner
|
@nbraud this PR also looks good. 👍 |
Pinning exact versions makes software that share dependencies essentially-impossible to install in the same environment. See #243. We use the “compatible version” operator, `~=`, to specify version constraints, essentially assuming that our dependencies follow SemVer.
23ca16e to
670dd37
Compare
Collaborator
Author
|
bors r=duckinator |
Contributor
|
Build succeeded: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pinning exact versions makes software that share dependencies essentially-impossible to install in the same environment. See #243 for an example of this kind of issue.
We use the “compatible version” operator,
~=, to specify version constraints, essentially assuming that our dependencies follow SemVer.