-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
read_csv interprets index column as dates #225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hm, this is caused by a bit of legacy cruft. Perhaps it's time to add a |
Alright, I'm just going to do this. I also am going to change the default for index_col to None-- I don't like breaking APIs but in retrospect index_col=0 was the wrong default. In certain cases (there the number of names in the header is 1 less than the number of columns of data) it should be able to auto-infer that the index_col=0, however (there is a test for this, I think) |
Oh, you're already addressing the next issue I filed. Kudos for responding so quickly! |
Again, tragic to break APIs but changing to |
Sure, I'll see what I can do. Presumably this makes the next release 0.5, rather than 0.4.4, since APIs are changing. |
That seems like a good idea. If any urgent bug fixes come along I can create a 0.4.x maintenance branch for cherry-picking, otherwise, I suppose I can target end of month or early November for a 0.5 release. Lot of stuff I want to do before then. |
I loaded a dataset with an index column going from 1 to 304. Then I try to get the repr of the dataframe, but it raises
ValueError: year=100 is before 1900; the datetime strftime() methods require year >= 1900
. Looking atdf.index
shows that the numeric indices have been transformed into datetimes (the first 31 to days of this month, 32-60 as years 20xx, 61-99 as years 19xx, and higher numbers as a raw year).The text was updated successfully, but these errors were encountered: