Ok, then this looks like a legitimate bug in span_where(). It probably
isn't applying units, somehow. This isn't really a problem with pandas, it
is an issue where we aren't being consistent in applying units for all
plotting functions. Could you file a bug report, please?
Cheers!
Ben Root
On Tue
On 02.12.2014 16:59, Benjamin Root wrote:
> Does the workaround posted here fix things for you?
> https://github.com/matplotlib/matplotlib/issues/3727#issuecomment-60899590
sorry it doesn't.
I updated the test case below (including the workaround, I hope I got it
right). The strange thing is tha
OK I just filled a bug report:
https://github.com/matplotlib/matplotlib/issues/3872
my first bug report ever!
On 02.12.2014 17:15, Fabien wrote:
> On 02.12.2014 16:59, Benjamin Root wrote:
>> Does the workaround posted here fix things for you?
>> https://github.com/matplotlib/matplotlib/issues/3
Does the workaround posted here fix things for you?
https://github.com/matplotlib/matplotlib/issues/3727#issuecomment-60899590
On Tue, Dec 2, 2014 at 10:43 AM, Fabien wrote:
> On 02.12.2014 16:34, Benjamin Root wrote:
> > Please provide the full traceback
>
> sure, I pasted the traceback below.
On 02.12.2014 16:34, Benjamin Root wrote:
> Please provide the full traceback
sure, I pasted the traceback below. Here are the pandas infos:
In [17]: df.info()
DatetimeIndex: 5 entries, 1950-01-01 00:00:00 to 1950-05-01 00:00:00
Freq: MS
Data columns (total 2 columns):
data5 non-null int64
c
Please provide the full traceback. Could you also show df.info()? In any
case, I suspect that the problem is that pandas recently started using
datetime64 for their timeseries, and matplotlib hasn't implemented the unit
converter for it. There was a post recently showing how to add pandas's
convert
