We would like the fmu-sumo (and sumo-wrapper-python) packages to be released to PyPI.
This would simplify downstream usage (git not needed in Docker image, and pip/poetry install/update commands are simplified).
In addition, currently it is hard to both pin fmu-sumo and sumo-wrapper-python versions used downstream, because if they are both e.g. pinned to their latest versions, we get
Because fmu-sumo (0.3.7) @ git+https://github.com/equinor/fmu-sumo.git@main depends on sumo-wrapper-python (*) @ git+https://github.com/equinor/sumo-wrapper-python.git@main
and backend depends on sumo-wrapper-python (0.3.3) @ git+https://github.com/equinor/sumo-wrapper-python.git@0.3.3, fmu-sumo is forbidden.
So, because backend depends on fmu-sumo (0.3.7) @ git+https://github.com/equinor/fmu-sumo.git@0.3.7, version solving failed.
We would like the
fmu-sumo
(andsumo-wrapper-python
) packages to be released to PyPI.This would simplify downstream usage (
git
not needed in Docker image, andpip
/poetry
install/update commands are simplified).In addition, currently it is hard to both pin
fmu-sumo
andsumo-wrapper-python
versions used downstream, because if they are both e.g. pinned to their latest versions, we getprobably due to
fmu-sumo
requiringmain
branch "version" ofsumo-wrapper-python
: https://github.com/equinor/fmu-sumo/blob/e8970433247f04050344f54397e4acbc57d5ad1d/requirements/requirements.txt#L4