The datastore, by using the datagetter as a library, has a hard connection to the datagetter's requirements.
This PR updates the entries in requirements.in to be a range compatible with the previously pinned versions in requirements.txt, based on versions that each library's documentation or changelog says have no relevant breaking changes. I've tested that the datagetter works with a simple ./datagetter.py --limit-downloads 10 with and without a cache, on Python 3.8 and 3.10.
Particularly with the two "CoVE compatibility" pins, I haven't (yet) checked if newer versions do actually work, beyond the breaking change being removed support for pre-3.8 Python versions, so it's possible we could go newer.
The datastore, by using the datagetter as a library, has a hard connection to the datagetter's requirements.
This PR updates the entries in
requirements.in
to be a range compatible with the previously pinned versions inrequirements.txt
, based on versions that each library's documentation or changelog says have no relevant breaking changes. I've tested that the datagetter works with a simple./datagetter.py --limit-downloads 10
with and without a cache, on Python 3.8 and 3.10.Particularly with the two "CoVE compatibility" pins, I haven't (yet) checked if newer versions do actually work, beyond the breaking change being removed support for pre-3.8 Python versions, so it's possible we could go newer.