add min xarray pin on run and numpy py ver linters #536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@dcherian feel free to close this b/c it may not fit your ideas. I thought it was odd that a min pin is necessary to build cf_xarray but not to run. That can lead to slower solves and, if there is a
xarray>=2022.03.0
feature necessary at run time, one can create a broken environment the way it is.I also bumped the linters to use the min support Python version. However, I'm pretty sure ruff reads
requires-python
if you omit those, reducing the amount of things to remember to edit at every version bump.