issue_comments: 457131090
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/1756#issuecomment-457131090 | https://api.github.com/repos/pydata/xarray/issues/1756 | 457131090 | MDEyOklzc3VlQ29tbWVudDQ1NzEzMTA5MA== | 28786187 | 2019-01-24T09:40:01Z | 2019-01-24T09:40:01Z | CONTRIBUTOR | Hi, Sorry for the late comment about a closed bug. But I find changing the API a bit irritating to say the least, and this is a serious change. Although apparently not many people use it, some actually may (myself included). And so far there has been only one bug report, so what problem are you trying to fix? I can fix my own code but there may be others out there that cannot keep pace with the development and including their packages may then break software. For my taste the deprecation warning is a bit short if you are going to remove such a feature already in the next version. A few more cycles would be appreciated. At the very least put a big warning sign to the documentation that xarray is still beta and the API is still subject to change. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
278713328 |