pull_requests: 1487073982
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1487073982 | PR_kwDOAMm_X85YovK- | 8107 | closed | 0 | Better default behavior of the Coordinates constructor | 4160723 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` After working more on `Coordinates` I realize that the default behavior of its constructor could be more consistent with other Xarray objects. This PR changes this default behavior such that: - Pandas indexes are created for dimension coordinates if `indexes=None` (default). To create dimension coordinates with no index, just pass `indexes={}`. - If another `Coordinates` object is passed as input, its indexes are also added to the new created object. Since we don't support alignment / merge here, the following call raises an error: `xr.Coordinates(coords=xr.Coordinates(...), indexes={...})`. This PR introduces a breaking change since `Coordinates` are now exposed in v2023.8.0, which has just been released. It is a bit unfortunate but I think it may be OK for a fresh feature, especially if the next release will be soon after this one. | 2023-08-23T21:42:51Z | 2024-02-04T18:32:42Z | 2023-08-31T07:35:47Z | 2023-08-31T07:35:47Z | 0f9f790c7e887bbfd13f4026fd1d37e4cd599ff1 | 0 | bce000cff6be4cf9d42454da4c370685e9dad051 | 42d42bab5811702e56c638b9489665d3c505a0c1 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8107 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests