pull_requests: 1702704223
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1702704223 | PR_kwDOAMm_X85lfTRf | 8684 | closed | 0 | Enable `numbagg` in calculation of quantiles | 56583917 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #7377 - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Just saw your message in the related issue @max-sixty. This is what I came up with earlier. I also did a quick test, comparing the calculation with and without using numbagg for a dummy 3D DataArray. I was only wondering if the default usage of numbagg (given that it's available and `method='linear'`) should be noted somewhere in the docstrings and/or the docs in general. | 2024-01-30T18:59:55Z | 2024-02-11T22:31:26Z | 2024-02-07T16:28:04Z | 2024-02-07T16:28:04Z | 0eb66587c44411abc668e96881a51e1b99e1eb9e | 0 | 18ef827afd0f4b35a014ab987ca559eddece98bb | f33a632bf87ec29dd9346f9b01ad4eec2194f72a | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/8684 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests