Bug report
Bug summary
When using a datetime x-axis in a pcolormesh, and nearest shading,
TypeError: '>=' not supported between instances of 'datetime.timedelta' and 'int'
is raised.
From what I can tell, #18398 assumed comparison with 0 would always be possible, but this isn't the case for datetime.timedelta.
Code for reproduction
from datetime import datetime
from matplotlib import pyplot as plt
x_coords = [datetime.fromtimestamp(x * 3600) for x in range(24)]
y_coords = [*range(0, 10)]
plt.pcolormesh(x_coords,
y_coords, [[*range(24)] for _ in range(10)],
shading="nearest")Actual outcome
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File ".local/lib/python3.8/site-packages/matplotlib/pyplot.py", line 2801, in pcolormesh
__ret = gca().pcolormesh(
File ".local/lib/python3.8/site-packages/matplotlib/__init__.py", line 1438, in inner
return func(ax, *map(sanitize_sequence, args), **kwargs)
File ".local/lib/python3.8/site-packages/matplotlib/axes/_axes.py", line 6093, in pcolormesh
X, Y, C, shading = self._pcolorargs('pcolormesh', *args,
File ".local/lib/python3.8/site-packages/matplotlib/axes/_axes.py", line 5651, in _pcolorargs
X = _interp_grid(X)
File ".local/lib/python3.8/site-packages/matplotlib/axes/_axes.py", line 5633, in _interp_grid
if not (np.all(dX >= 0) or np.all(dX <= 0)):
TypeError: '>=' not supported between instances of 'datetime.timedelta' and 'int'
Expected outcome
None
Matplotlib version
- Matplotlib version: 3.3.2
- Python version: 3.8
works with pip3 install matplotlib==3.3.1, fails with pip3 install matplotlib==3.3.2
Bug report
Bug summary
When using a datetime x-axis in a pcolormesh, and nearest shading,
is raised.
From what I can tell, #18398 assumed comparison with 0 would always be possible, but this isn't the case for
datetime.timedelta.Code for reproduction
Actual outcome
Expected outcome
None
Matplotlib version
works with
pip3 install matplotlib==3.3.1, fails withpip3 install matplotlib==3.3.2