Update requirements and deprecated code #122
Merged
Conversation
This file contains 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
|
I can see what you've done and the branch runs fine locally for me but I'll leave to @volcan01010 to confirm and merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR addresses #121 by loosening the pinned versions in
requirements.txtto less than the next major version. This should allow the packages to be updated through re-deployment without having to modifyrequirements.txtrepeatedly. At the same time there should be no breaking changes.The versions have been unpinned completely in
requirements_dev.txt.Updates also have been made to remove deprecated code, highlighted as warnings in the
pytestresults, inpydanticandhttpx. Other deprecation warnings result from upstream packages over which we have little control.The tests should all pass.