-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you really need the newest xarray>=2023 dependency? #35
Comments
Can you expand on which setting would not allow bumping xarray>=2023 ? Unlike libraries like Moreover, what's preventing the occasional users that really can't install this requirement to simply install an older version of
|
In typical circumstances yes, but not so easily on larger cluster systems or scientific environments where very often only certain Python environments and setups are supported and going outside them (e.g installing a a user pip or conda env) can be very difficult (loss of functionality in terms of specialized libraries). Often they may even have xarray installed and used by some software, but an older version than 2023.
This may indeed be a workaround for those that really need it, but such a hurdle needlessly lowers the possible appeal of
If the |
I'd agree with you if the test suite was actually complete, but as it stands only If you feel like adding more test coverage (via PR), I'd be happy to integrate it and then find the oldest version of xarray that pass all tests. |
xrscipy used to work just fine with older xarray versions, so unless you really need
xrscipy>=2023
, please don't introduce such a strict dependency which prevents simple xrscipy installation in older environments (in scientific environments and clusters one does not always have a choice).The text was updated successfully, but these errors were encountered: