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.
Thanks again for releasing togglwrapper.
While pinning all dependencies in CI is a good idea to avoid contributors having to deal with spurious version-upgrade problems as they're trying to contribute unrelated fixes, it's unfortunately a problem for applications, which need to upgrade their dependencies on a more regular cadence than togglwrapper maintenance has bandwidth for. There's always the possibility of a new version of
requests
breaking things, but that's really the responsibility of therequests
maintainers to keep things working.This distinction between
setup.py
andrequirements.txt
is somewhat subtle, but Donald Stufft tried to explain it in some depth here: https://caremad.io/posts/2013/07/setup-vs-requirement/Separately from this PR, it might be good to
get a (free!) account on Requires.io,turn on Dependabot which can automatically send you a PR when any of your Python dependencies upgrade, which will take care of bothrequirements.txt
andtest_requirements.txt
for you.