-
Notifications
You must be signed in to change notification settings - Fork 51
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
Remove calls to rio.parse_path (maintain compat with rasterio==1.3) #155
Conversation
parse_path is being deprecated in rasterio 1.3 and removed in 1.4 https://github.com/rasterio/rasterio/blob/d761b0ed0c9aecee47355d8d1852ca45c4be5b85/CHANGES.txt#L61 It is called internally anyway by DatasetBase https://github.com/rasterio/rasterio/blob/d761b0ed0c9aecee47355d8d1852ca45c4be5b85/rasterio/_base.pyx#L290
NB: No formatting applied (to keep diff small), but happy to |
We're constructing rasterio Based on rasterio/rasterio#2428, it sounds to me like the changes in this PR (passing raw strings into the |
Yeah sorry, should have marked this as a draft/discussiony PR. In the meantime should probably lock down the rasterio dep, otherwise standard installs will break as soon as diff --git a/pyproject.toml b/pyproject.toml
-rasterio = "^1.2.3"
+rasterio = "~1.2.3" And then make the change from this PR + upgrade to |
Let's just make the rasterio change in this PR as well. It looks like someone who installs stackstac today and gets the new rasterio will have things fail: microsoft/PlanetaryComputer#80 (comment). This is quite an urgent fix. As soon as this is in, I'll cut a release. |
Ah I see, rasterio 1.3.X is still in pre-release: https://pypi.org/project/rasterio/#history. I don't quite understand how a PC user ended up with a pre-release version then: microsoft/PlanetaryComputer#80 (comment). In that case, I agree. We should make and release this change right now: diff --git a/pyproject.toml b/pyproject.toml
-rasterio = "^1.2.3"
+rasterio = "~1.2.3" Then merge this PR and switch to |
FYI 1.3 is going to be published today or tomorrow rasterio/rasterio#2310 (comment) |
PR here with the rasterio constraint: #157 Regarding people having rasterio |
Still needs a `poetry lock` once 1.3.0 is released
@carderne rasterio's got your back: rasterio/rasterio@5d5d946. |
Thanks so much @sgillies! Once 1.3.0 is out, we can merge this and release, but that takes the time pressure off. |
Open source saves the day! |
More absurdity from python-poetry/poetry#5121. If I remove the `coiled` dependency, locking takes ~1min.
rasterio.path
(and therefore,rasterio.parse_path
) is being deprecated in rasterio 1.3 and removed in 1.4.It is called internally anyway by DatasetBase so shouldn't be necessary to call it while
init
ing.Have checked that this works for my use case, YMMV.