pull_requests: 1797701340
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1797701340 | PR_kwDOAMm_X85rJr7c | 8888 | open | 0 | to_base_variable: coerce multiindex data to numpy array | 4160723 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #8887, and probably supersedes #8809 - [x] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - ~~New functions/methods are listed in `api.rst`~~ @slevang this should also make work your test case added in #8809. I haven't added it here, instead I added a basic check that should be enough. I don't really understand why the serialization backends (zarr?) do not seem to work with the `PandasMultiIndexingAdapter.__array__()` implementation, which should normally coerce the multi-index levels into numpy arrays as needed. Anyway, I guess that coercing it early like in this PR doesn't hurt and may avoid the confusion of a non-indexed, isolated coordinate variable that still wraps a pandas.MultiIndex. | 2024-03-29T10:10:42Z | 2024-03-29T15:54:19Z | 0f5c78efff8fdc024de20a178acf3ae7ac62f84e | 0 | dd9c3b4ad88b6694b6e737e86e80ad1dcfa1527c | 2120808bbe45f3d4f0b6a01cd43bac4df4039092 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8888 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests