pull_requests: 1197041777
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1197041777 | PR_kwDOAMm_X85HWWhx | 7437 | open | 0 | DRAFT: Implement `open_datatree` in BackendEntrypoint for preliminary DataTree support | 3460034 | <!-- Feel free to remove check-list items aren't relevant to your change --> As discussed among folks at today's Pangeo working meeting (cc @jhamman, @TomNicholas), we are looking to try adding support for `DataTree` in the Backend API, so that backend engines can readily add `DataTree` capability. For example, with `cfgrib`, we could have ```python import xarray as xr dt = xr.open_datatree("path/to/gribfile.grib", engine="cfgrib") ``` given that `cfgrib` implements the appropriate method to their `BackendEntrypoint` subclass. Similarly, with NetCDF files or Zarr stores with groups, we could open as `DataTree` to obviate the need to specify a single group. Working Design Doc: https://hackmd.io/Oqeab-54TqOOHd5FdCb5DQ?edit xref https://github.com/ecmwf/cfgrib/issues/327, https://github.com/openradar/xradar/issues/7 - ~~Closes #xxxx~~ - [ ] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` | 2023-01-13T17:17:41Z | 2023-07-31T10:09:18Z | 4210ae92dbfaf917c5b5ebc7e30754936f87a258 | 1 | 9d64b3657142474d99d2cfbb1b1db6a56ae324f3 | 3ee7b5a63bb65ce62eff3dafe4a2e90bca7a9eeb | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/7437 |
Links from other tables
- 3 rows from pull_requests_id in labels_pull_requests