-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
Handling of trailing delimiters in read_csv #2442
Comments
To reproduce the bug, just create a two-line csv file. The first line is the header, without trailing delimiter. The second line is data, with trailing delimiter. Then |
This is very annoying because the index/row name inference is very useful in most cases, but breaks down in the case where you have a malformed file. I'll think about it some |
Hmmm...custom dialect option? |
Probably should have an option like index_col=False and deal with an empty column. I have the latest FEC file (which has ballooned--!!-- to 900+MB) to try it out |
While we are on it, may I suggest a feature about So having an option to tell |
Already done in the development version of pandas-- you should install it. |
I wrote a blog about this, enjoy: http://wesmckinney.com/blog/?p=635 |
Blog link is dead. |
Trailing delimiters on data rows confusing the parser is still an unresolved issue as of 1.0:
and also, if we try to explicitly specify the (single) header row:
|
xref http://stackoverflow.com/questions/13719946/python-pandas-trailing-delimiter-confuses-read-csv
The text was updated successfully, but these errors were encountered: