Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't pin requests in setup.py #10

Merged
merged 1 commit into from
Mar 25, 2021
Merged

don't pin requests in setup.py #10

merged 1 commit into from
Mar 25, 2021

Conversation

glyph
Copy link
Contributor

@glyph glyph commented Feb 7, 2020

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 the requests maintainers to keep things working.

This distinction between setup.py and requirements.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 both requirements.txt and test_requirements.txt for you.

@glyph
Copy link
Contributor Author

glyph commented Apr 5, 2020

Bump?

@glyph
Copy link
Contributor Author

glyph commented Aug 19, 2020

Anything I can do to facilitate this getting merged?

As you can see here pypa/pip#988 (comment) pip has now merged their constraint-based dependency resolver, which means that this overly-strict constraint is eventually going to start breaking installs of things that use togglwrapper whereas it would previously only show a warning.

@aarose
Copy link
Owner

aarose commented Mar 25, 2021

@glyph Thank you so much for your contribution! 🙏 And for everyone's patience

@aarose aarose merged commit d2ea18d into aarose:develop Mar 25, 2021
@aarose
Copy link
Owner

aarose commented Mar 25, 2021

and TIL about the difference between the two (requirements.txt vs setup), thank you.

aarose added a commit that referenced this pull request Mar 25, 2021
don't pin `requests` in setup.py
@glyph glyph deleted the versions branch March 25, 2021 08:13
@glyph
Copy link
Contributor Author

glyph commented Mar 25, 2021

Thanks so much for the continued maintenance @aarose ! I know how hard it can be to make time for open source stuff particularly in this past year.

Do you have plans for a PyPI release soon?

@aarose
Copy link
Owner

aarose commented Mar 25, 2021

Yeah, version 1.2.1 should be out now!

@glyph
Copy link
Contributor Author

glyph commented Mar 25, 2021

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants