Bump and relax xarray version requirement #51
Comments
|
Probably should just relax it, though in this case we might actually want to bump—looks like there are a couple things in the new xarray version that will benefit stackstac visualizations (faster interp logic + fixed |
gjoseph92
added a commit
to gjoseph92/geogif
that referenced
this issue
May 7, 2021
Necessary for gjoseph92/stackstac#51. We have to do a crazy dance because of python-poetry/poetry#697. **This lockfile is out of date. I've manually overridden `pyproject.toml` to an unsolveable state in order to bump the xarray version and cut a release.** This will be resolved in a future commit.
gjoseph92
added a commit
to gjoseph92/geogif
that referenced
this issue
May 7, 2021
Necessary for gjoseph92/stackstac#51. We have to do a crazy dance because of python-poetry/poetry#697. **This lockfile is out of date. I've manually overridden `pyproject.toml` to an unsolveable state in order to bump the xarray version and cut a release.** This will be resolved in a future commit.
gjoseph92
added a commit
that referenced
this issue
May 7, 2021
Closes #51 Allow `xarray >=0.18,<1`. Also just require `^0` for non-critical packages that aren't 1.0 yet.
gjoseph92
added a commit
that referenced
this issue
May 7, 2021
Closes #51 Allow `xarray >=0.18,<1`. Also just require `^0` for non-critical packages that aren't 1.0 yet.
|
stackstac 0.2.1 is out, give it a try! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From #50 (@scottyhq):
Also, I'm wondering if it's possible to relax (^0) or bump (^0.18.0) the current xarray pin for the next release? Could add some matrix tests against xarray master to ensure things don't break since currently it does seem like minor bumps in xarray are more like major bumps ;) (#26 ).
stackstac/pyproject.toml
Line 43 in d1e15ca
The text was updated successfully, but these errors were encountered: