Dependency versions need to be constrained #10
Description
Roguewave currently does not have any version specification for its dependencies. Other Sofar projects rely on roguewave as a dependency:
- esm-assessment
- wx-data-workbench
- forecast-skill-monitoring
As a result, there is much friction introduced in the development of these projects, as it is very difficult to install as one must manually resolve roguewave's dependencies and versioning must be established downstream.
The versioning has been resolved by @johnorcutt to an extent in wx-data-workbench, but additional testing is needed to verify that these versions are comprehensive enough and compatible with other modules in roguewave that are not utilized in wx-data-workbench.
Context:
Conversation between @johnorcutt / @ciaradorsay:
Good morning John!
I pushed some changes to wx-data-workbench that included additions to the toml file to install all of the dependencies for wx-assessment-plots. Pushing these changes failed, it appears on installations related to those dependencies. It is not obvious to me why this is happening, as the error happens when tzdata is downgraded from 2025.2 to 2025.1 (though in the poetry.lock file for wx-assessment-plots, the version of tzdata is 2025.1 anyways). When you have some time would you mind taking a quick look and letting me know if you have any recommendations for trouble shooting to try?
ahhhh yeah, we have to keep Python and all of the dependencies pinned to the specified version in wx-data-workbench because of roguewave. So we will need to use older versions of Python, xarray, numpy, etc in the plots library for the time being as well.
Roguewave does not specify versions for the required dependencies, which would mean with a pip install requirements the newest versions would be downloaded. Why do we need to use older versions and how did you determine which versions to use?
It wouldn't work with any newer version - Lots of trial and error until it finally worked.