issue_comments: 554980168
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/pull/3537#issuecomment-554980168 | https://api.github.com/repos/pydata/xarray/issues/3537 | 554980168 | MDEyOklzc3VlQ29tbWVudDU1NDk4MDE2OA== | 6213168 | 2019-11-18T11:42:04Z | 2019-11-18T11:42:04Z | MEMBER |
Pre-empting an observation: yes, the nanmin function I wrote could be used to work around the shortcomings of both numpy and dask on datetime64. I don't think xarray should do it and IMHO the workaround currently implemented for mean() should never have been done to begin with. Again, this PR only fixes the regression on numpy 1.18. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
523438384 |