pull_requests: 1046566934
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1046566934 | PR_kwDOAMm_X84-YVgW | 6992 | closed | 0 | Review (re)set_index | 4160723 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes - [x] fixes #6946 - [x] fixes #6989 - [x] fixes #6959 - [x] fixes #6969 - [x] fixes #7036 - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Restore behavior prior to the explicit indexes refactor (i.e., refactored but without breaking changes). TODO: - [x] review `set_index` - [x] review `reset_index` For `reset_index`, the only behavior that is not restored here is the coordinate renamed with a `_` suffix when dropping a single index. This was originally to prevent any coordinate with no index matching a dimension name, which is now irrelevant. That is a quite dirty workaround and I don't know who is relying on it (no complaints yet), but I'm open to restore it if needed (esp. considering that we may later deprecate `reset_index` completely in favor of `drop_indexes` #6971). | 2022-09-05T15:07:43Z | 2023-08-30T09:05:10Z | 2022-09-27T10:35:38Z | 2022-09-27T10:35:38Z | a042ae69c0444912f94bb4f29c93fa05046893ed | 0 | ca01949cb889ee38aae33560b02de1f7625fd921 | 45c0a114e2b7b27b83c9618bc05b36afac82183c | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/6992 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests