pull_requests: 1824051470
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1824051470 | PR_kwDOAMm_X85suNEO | 8946 | open | 0 | Fix upcasting with python builtin numbers and numpy 2 | 1828519 | See #8402 for more discussion. Bottom line is that numpy 2 changes the rules for casting between two inputs. Due to this and xarray's preference for promoting python scalars to 0d arrays (scalar arrays), xarray objects are being upcast to higher data types when they previously didn't. I'm mainly opening this PR for further and more detailed discussion. CC @dcherian - [ ] Closes #8402 - [ ] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` | 2024-04-15T20:07:42Z | 2024-04-29T12:38:55Z | 9db1a51b4d15279fb91d1f8802a1139ee5e76c18 | 0 | 5b4384fe279abc8eb0b8a4b18c2696e82c59285a | 9eb180b7b3df869c21518a17c6fa9eb456551d21 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/8946 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests