issue_comments: 514880353
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/525#issuecomment-514880353 | https://api.github.com/repos/pydata/xarray/issues/525 | 514880353 | MDEyOklzc3VlQ29tbWVudDUxNDg4MDM1Mw== | 1217238 | 2019-07-25T03:25:47Z | 2019-08-24T05:02:39Z | MEMBER | I think we could do basic indexes with units after steps (1) and (2) in the big index refactor plan: https://github.com/pydata/xarray/issues/1603#issuecomment-511126208 At that point, indexes will be something that are propagated entirely separately from arrays. So even if the index will get cast into a pandas.index, the corresponding coordinate array will stick around. The next level of support would be "unit array indexing", e.g., |
{
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
100295585 |