The FAIR Data Registry is a Django website and REST API which is used by the FAIR Data Pipeline to store metadata about code runs and their inputs and outputs
Currently we have 3 different requirements files:
local-requirements.txt - for the local registry
requirements.txt - for the remote registry
pyproject.toml - poetry requirements, currently only used for the CI
The issue arises keeping these all synced and ensuring none of the older versions of theses requirements break (recently LXML broke
on MAC OS ARM which is a requirement of prov and a specific version was added to the local-requirements.txt to overcome this). I understand we may not want to use greater than in these requirements.txt files without prior testing, but we need to consolidate the requirements possibly using poetry and using the CI with a weekly build to see if any of the requirements cause issues.
Currently we have 3 different requirements files: local-requirements.txt - for the local registry requirements.txt - for the remote registry pyproject.toml - poetry requirements, currently only used for the CI
The issue arises keeping these all synced and ensuring none of the older versions of theses requirements break (recently LXML broke on MAC OS ARM which is a requirement of prov and a specific version was added to the local-requirements.txt to overcome this). I understand we may not want to use greater than in these requirements.txt files without prior testing, but we need to consolidate the requirements possibly using poetry and using the CI with a weekly build to see if any of the requirements cause issues.