pull_requests: 509227316
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 509227316 | MDExOlB1bGxSZXF1ZXN0NTA5MjI3MzE2 | 4530 | closed | 0 | document the duck array integration status | 14808389 | With the initial (experimental) release of `pint-xarray` getting closer (see xarray-contrib/pint-xarray#25), I figured it might make sense to document the parts of the API of `xarray` which right now won't work with duck arrays, and to start maintaining a list of extensions like `pint-xarray`. The remaining issues are taken from #3594, but I'm sure I missed something (e.g. plotting). - [x] Passes `isort . && black . && mypy . && flake8` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2020-10-23T21:33:36Z | 2020-11-20T21:55:47Z | 2020-11-20T21:04:21Z | 2020-11-20T21:04:20Z | a2192158e3fbb94b2d972ff3e1693fffa65e50be | 0 | 56228986b6fb65eaf42bce334047e0417acc3691 | ef910b9f40f7ebe6528781a1418ddc40915952bb | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/4530 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests