issue_comments: 194976812
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/789#issuecomment-194976812 | https://api.github.com/repos/pydata/xarray/issues/789 | 194976812 | MDEyOklzc3VlQ29tbWVudDE5NDk3NjgxMg== | 1197350 | 2016-03-10T17:56:27Z | 2016-03-10T17:56:27Z | MEMBER | :+1: I hit this problem months back when analyzing CESM runs. It seems silly that the adoption of xarray by the climate modeling community should rest on these highly technical issues. But that seems to be the reality. The challenge is to raise the profile of these issues within the numpy and pandas communities such that they become a high priority. Even better would be dedicated developer time (e.g. from someone at UNIDATA) to implement fixes. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
139956689 |