issue_comments: 283062107
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/1288#issuecomment-283062107 | https://api.github.com/repos/pydata/xarray/issues/1288 | 283062107 | MDEyOklzc3VlQ29tbWVudDI4MzA2MjEwNw== | 1197350 | 2017-02-28T14:59:54Z | 2017-02-28T14:59:54Z | MEMBER | Having an xarray wrapper on I will also make the same comment I always make when such feature requests are raised: yes, it always seems desirable to add new features to xarray on a function-by-function basis. But where does it end? Why not implement the rest of the scipy.ode module? And why stop there? As a community we need to develop a roadmap that clearly defines the scope of xarray. Once |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
210704949 |