You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading this blog post, I'm convinced that we should not be using upper bound constraints for our dependencies.
tl;dr It is much more of a headache for users if libraries add upper version constraints. The author gives in depth reasons and suggested ways to avoid upper version constraints.
Proposal
Remove all upper version constraints (< and ~).
Add a job that installs with --pre and runs our tests
Do not merge a PR that causes the --pre job to fail
Description
After reading this blog post, I'm convinced that we should not be using upper bound constraints for our dependencies.
tl;dr It is much more of a headache for users if libraries add upper version constraints. The author gives in depth reasons and suggested ways to avoid upper version constraints.
Proposal
<
and~
).--pre
and runs our tests--pre
job to fail--pre
jobpytest
withfilterwarnings=error
The text was updated successfully, but these errors were encountered: