Closed danmd closed 11 years ago
This turned out to be a really esoteric case! In 0.11, we enabled time-series slicing via string shortcuts
The following is a normal selection via string based time-series slicingthe
In [7]: df = DataFrame(randn(10,2),index=date_range('20600101',periods=10,freq='Q'))
In [8]: df
Out[8]:
0 1
2060-03-31 0.805302 1.483985
2060-06-30 -0.606980 -0.722344
2060-09-30 -0.715166 -0.065888
2060-12-31 0.086402 2.754483
2061-03-31 -0.578437 -0.262175
2061-06-30 1.016819 -1.214755
2061-09-30 0.691813 0.954097
2061-12-31 0.757279 1.573809
2062-03-31 -0.666067 -1.630134
2062-06-30 0.071744 -0.988124
In [9]: df['2060']
Out[9]:
0 1
2060-03-31 0.805302 1.483985
2060-06-30 -0.606980 -0.722344
2060-09-30 -0.715166 -0.065888
2060-12-31 0.086402 2.754483
However, for some really weird reason, 'T060' (and only that) parses out to a equivalent to '2060' must be a shortcut some how
In [10]: df['T060']
Out[10]:
0 1
2060-03-31 0.805302 1.483985
2060-06-30 -0.606980 -0.722344
2060-09-30 -0.715166 -0.065888
2060-12-31 0.086402 2.754483
I fixed this another way, in any event
thanks for the report
@wesm take a look at this!
closed by #3597
version 0.11.0 has introduced a confusing behavior when importing data via read_fwf (and, I'm pretty sure, read_table)
With version 0.10.1
and, with version 0.11.0
No matter how many columns I've been importing (up to 32 in some cases), it seems like it is always the 5th and 6th columns getting hit.