This pins all dependencies in requirements.txt to a specific version number. This will make deployments and builds more deterministic and ensure that builds don't randomly break because new versions of dependencies with breaking changes have been released. It also ensures that we don't receive tons of DeprecationWarning spam.
For the most part, it just replaces all >='s with ==. Exceptions noted below via GitHub comments.
The flip side of this change, of course, is that it's on our shoulders to make sure we're using the most recently bug-fixed versions of our dependencies, and that they're not spamming DeprecationWarnings on us.
This pins all dependencies in
requirements.txtto a specific version number. This will make deployments and builds more deterministic and ensure that builds don't randomly break because new versions of dependencies with breaking changes have been released. It also ensures that we don't receive tons ofDeprecationWarningspam.For the most part, it just replaces all
>='s with==. Exceptions noted below via GitHub comments.The flip side of this change, of course, is that it's on our shoulders to make sure we're using the most recently bug-fixed versions of our dependencies, and that they're not spamming
DeprecationWarnings on us.