APIv2: pass user defined filename_or_obj
to backends as is
#4707
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.
isort . && black . && mypy . && flake8
whats-new.rst
The change affects only APIv2.
Pros:
open_dataset
passes the dataset description objectfilename_or_obj
to the backends without fiddling with it. This is more and more important as several backends know how to opendict
s,file
'sstr
s that are not paths (rasterio for example accepts GDAL strings that are not paths and that is one of the reasonsengine="rasterio"
cannot be used inopen_dataset
)Cons: