issue_comments: 238737474
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/956#issuecomment-238737474 | https://api.github.com/repos/pydata/xarray/issues/956 | 238737474 | MDEyOklzc3VlQ29tbWVudDIzODczNzQ3NA== | 1217238 | 2016-08-10T00:58:45Z | 2016-08-10T00:58:45Z | MEMBER | I think it's important to preserve the ability to work with non-unique indexes insofar as it is necessary for cleaning your data. That's why we support non-unique indexes in merge, which is internally used anytime you assign to a Dataset. I'm less sure about the use cases for arithmetic and the like. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
170259709 |