issue_comments: 1336302962
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/7350#issuecomment-1336302962 | https://api.github.com/repos/pydata/xarray/issues/7350 | 1336302962 | IC_kwDOAMm_X85Ppl1y | 1217238 | 2022-12-04T02:16:25Z | 2022-12-04T02:16:25Z | MEMBER | This was an intentional design choice, back in the early days of Xarray. The rule Xarray uses for choosing which coordinates to associate with a DataArray created from a Dataset or DataArray is "every coordinate whose dimensions are still present on the new DataArray." This includes scalar coordinates, which are always kept around (because their dimensions are always included). What rule would you suggest instead? I agree that the behavior in this case "feels" wrong, but keep in mind that once |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1473329967 |