requirements.txt - Use minimal instead of exact versions - #179
Merged
Conversation
yprez
force-pushed
the
requirements-versions-up
branch
from
January 14, 2016 09:56
b71df74 to
4118a84
Compare
Merged
Owner
|
This was so needed! Merging and uploading into pypi asap |
codelucas
added a commit
that referenced
this pull request
Jan 25, 2016
requirements.txt - Use minimal instead of exact versions
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.
requirements.txt - Use minimal instead of exact versions
As suggested in #174
I took the current version in requirements.txt (assuming nothing breaks with them) and changed them to the minimal version.
Downgrading to the real minimal version that works at this point is too complicated and might introduce new undiscovered bugs.
Tested locally on a fresh virtualenv.