issue_comments: 552655149
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/2799#issuecomment-552655149 | https://api.github.com/repos/pydata/xarray/issues/2799 | 552655149 | MDEyOklzc3VlQ29tbWVudDU1MjY1NTE0OQ== | 1217238 | 2019-11-11T22:57:55Z | 2019-11-11T22:57:55Z | MEMBER |
Yes, I think this is still the case for slicing in xarray. There's just much larger constant overhead than in NumPy. (And this is difficult to fix short of rewriting xarray's core in C.) |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
416962458 |