by switching setup.py to use requirements.in instead of requirements.txt.
Now that requirements.in specifies compatible ranges, this allows downstream library uses to upgrade to compatible sub-requirement versions, e.g. for security updates, without needing to first update the requirements.txt in this repo.
by switching setup.py to use requirements.in instead of requirements.txt.
Now that requirements.in specifies compatible ranges, this allows downstream library uses to upgrade to compatible sub-requirement versions, e.g. for security updates, without needing to first update the requirements.txt in this repo.