⭐🐍 pyopencdms aims to build a common Python API on top of multiple Climate Data Management Systems (CDMS) that use different underlying database engines
MIT License
4
stars
6
forks
source link
Pinning dependency versions in requirements.txt #95
Currently the pyopencdms library is pinning exact versions of dependencies in our requirements.txt, e.g. SQLAlchemy~=1.4.46.
However, since pyopencdms is a library that is intended for reuse in different situations we should declare more flexible versions.
For example, for SQLAlchemy we should follow GeoAlchemy2 and pin SQLAlchemy>=1.4, <3 (or we should go even further and remove SQLAlchemy as an explicit dependency and instead get a suitable version via GeoAlchemy2).
However, when we deploy pyopencdms in our opencdms production stack (here) we should pin the exact version that we tested against (e.g. SQLAlchemy==2.0.0 which has just been released).
Currently the
pyopencdmslibrary is pinning exact versions of dependencies in our requirements.txt, e.g.SQLAlchemy~=1.4.46.However, since
pyopencdmsis a library that is intended for reuse in different situations we should declare more flexible versions.For example, for SQLAlchemy we should follow GeoAlchemy2 and pin
SQLAlchemy>=1.4, <3(or we should go even further and remove SQLAlchemy as an explicit dependency and instead get a suitable version via GeoAlchemy2).However, when we deploy
pyopencdmsin our opencdms production stack (here) we should pin the exact version that we tested against (e.g.SQLAlchemy==2.0.0which has just been released).