issue_comments: 663030222
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/4226#issuecomment-663030222 | https://api.github.com/repos/pydata/xarray/issues/4226 | 663030222 | MDEyOklzc3VlQ29tbWVudDY2MzAzMDIyMg== | 199813 | 2020-07-23T14:11:33Z | 2020-07-23T14:11:33Z | NONE | That changes was definitely intentional in BoundaryNorm, but we thought that we were giving a clear error in a case where you used to get a divide by 0 error. I think we used to implicitly change 1 boundary into a degenerate 2 boundary, I can see the argument that we should be more forgiving, but in boundry norm I'm not sure what that would mean (internally we are going to make every value to either over or under. If you want to support this at the xarray level you should do the [4] -> [4, 4] conversion which will work with all version of Matplotlib. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
657230088 |