issues: 2244518111
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2244518111 | PR_kwDOAMm_X85suNEO | 8946 | Fix upcasting with python builtin numbers and numpy 2 | 1828519 | open | 0 | 18 | 2024-04-15T20:07:42Z | 2024-04-29T12:38:55Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/8946 | 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
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8946/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |