issue_comments: 324822729
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/1512#issuecomment-324822729 | https://api.github.com/repos/pydata/xarray/issues/1512 | 324822729 | MDEyOklzc3VlQ29tbWVudDMyNDgyMjcyOQ== | 1217238 | 2017-08-25T04:44:54Z | 2017-08-25T04:44:54Z | MEMBER | pandas 0.18 came out in March 2016 (about 18 months ago by the time of our next release). I would be reluctant to require anything newer than NumPy 1.11, which also came out in March 2016. I don't see removing functions from npcompat as particularly good justification on its own. But if there is new functionality that requires a newer NumPy, then that could be a good reason to require something newer (especially if it's hard to backport). For example, if we required NumPy 1.13, then we could make use of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
251666172 |