issue_comments: 371718795
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/pull/1972#issuecomment-371718795 | https://api.github.com/repos/pydata/xarray/issues/1972 | 371718795 | MDEyOklzc3VlQ29tbWVudDM3MTcxODc5NQ== | 1562854 | 2018-03-09T05:38:23Z | 2018-03-09T05:38:23Z | CONTRIBUTOR | As pointed out on the matplotlib gitter: If you run ```python import numpy as np import xarray as xr import matplotlib.pyplot as plt for i in range(200):
xr.DataArray(np.array([[0, 0], [0, 0]], dtype=np.uint8)).plot.pcolormesh()
Are you sure your test isn't doing something similar? At some point there just isn't room for more colorbars! Adding a Its also is possible you are hitting floating point overflows with your test. At some point Matplotlib needs to be able to manipulate the data that comes in, and if you operate near the maximum number your data type can handle, you'll have problems. Just like you would if you just did
Matplotlib indeed has flaws and quirks, but if you are finding bugs it would be good to isolate them. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
303103716 |