issue_comments: 318426619
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/1493#issuecomment-318426619 | https://api.github.com/repos/pydata/xarray/issues/1493 | 318426619 | MDEyOklzc3VlQ29tbWVudDMxODQyNjYxOQ== | 1217238 | 2017-07-27T17:11:37Z | 2017-07-27T17:11:37Z | MEMBER | If we can finish up @fujiisoup's work (https://github.com/pydata/xarray/pull/1473) bringing indexing with broadcasting to xarray, then we can possibly do away with This doesn't resolve the issue of whether the indexed coordinates should be in a MultiIndex or not. This does make a certain amount of sense, but to be honest, I'm a little divided here -- I'm still not entirely happy with how MultiIndex works in xarray (see https://github.com/pydata/xarray/pull/1426 for more discussion). |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
245893358 |