issue_comments: 303270041
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/1420#issuecomment-303270041 | https://api.github.com/repos/pydata/xarray/issues/1420 | 303270041 | MDEyOklzc3VlQ29tbWVudDMwMzI3MDA0MQ== | 1217238 | 2017-05-23T02:09:15Z | 2017-05-23T02:09:15Z | MEMBER | If the new rule significantly better, then breaking changes are certainly possible (in a major release). But for bars should be high: it needs to be worth potential turmoil when users update their code. For example, we could argue that I'm not sure what rule we could use for dropping scalar coordinates in particular. Adding an exception to the rules for only scalar coordinates would be a non-starter. The only alternative rule that seems at all sensible is that indexed coordinates only have the minimal set of coordinates (i.e., equivalent to calling |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
230529125 |