issue_comments: 338779368
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/1650#issuecomment-338779368 | https://api.github.com/repos/pydata/xarray/issues/1650 | 338779368 | MDEyOklzc3VlQ29tbWVudDMzODc3OTM2OA== | 1217238 | 2017-10-23T20:02:12Z | 2017-10-23T20:02:12Z | MEMBER | This should be easier after the index/coordinates separation envisioned in https://github.com/pydata/xarray/issues/1603. We could potentially define a basic index API (based on what we currently use from pandas) and allow alternative index implementations. There are certainly other use cases where go beyond pandas makes sense -- a KDTree for indexing geospatial data is one obvious example. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
267628781 |