home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 652482831

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/4187#issuecomment-652482831 https://api.github.com/repos/pydata/xarray/issues/4187 652482831 MDEyOklzc3VlQ29tbWVudDY1MjQ4MjgzMQ== 2448579 2020-07-01T15:20:39Z 2020-07-01T15:20:39Z MEMBER

I wonder if it's really worth deprecating open_zarr(). open_dataset(..., engine='zarr') is a bit more verbose, especially with backend_kwargs to pass optional arguments. It seems pretty harmless to keep open_zarr() around, especially if it's just an alias for open_datraset(engine='zarr').

I agree. I think we should keep open_zarr around.

As reminder (because it took me a while to remember!), one goal with this refactor is to have open_mfdataset work with all backends (including zarr and rasterio) by specifying the engine kwarg.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  647804004
Powered by Datasette · Queries took 0.573ms · About: xarray-datasette