issue_comments: 482643387
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/525#issuecomment-482643387 | https://api.github.com/repos/pydata/xarray/issues/525 | 482643387 | MDEyOklzc3VlQ29tbWVudDQ4MjY0MzM4Nw== | 1217238 | 2019-04-12T16:44:16Z | 2019-04-12T16:44:16Z | MEMBER | (I just added a third bullet to my list above)
First, we'll need to wait for NumPy 1.17 to be released :). But more seriously, if we do a breaking release of xarray we can probably with bumping the required NumPy version significantly. It's definitely a smoother experience for users if we allow at least slightly older versions of NumPy (e.g., so they can use newer xarray with a version of NumPy pre-packaged with their system), but if keeping existing things working with the current version of NumPy is a pain, then it may be worth upgrading the minimum required version. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
100295585 |