-
Notifications
You must be signed in to change notification settings - Fork 390
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
Data('file.csv') no longer infers fields with string values #1254
Comments
I will solve it for now by passing an argument to force the first row to be interpreted as column names. http://pandas.pydata.org/pandas-docs/stable/generated/pandas.read_csv.html |
http://blaze.pydata.org/en/latest/csv.html#correcting-csv-dialects states: In the first case of incorrect guessing of CSV dialect (e.g. delimiter) Blaze respects and passes through all keyword arguments to pandas.read_csv. However
Moreover, pandas infers the fields as expected:
So for now the workaround is |
@bittlingmayer Pass d = Data('foo.csv', has_header=True) |
I'm going to add a test and a bit of documentation for this issue and then close it |
Documentation would be good, although I also think the original ie pandas behaviour is a bit smarter. |
@bittlingmayer Yes, it's smarter, however this is a compromise between being explicit and convenience |
On 0.8.0 this worked. But since I updated, instantiating Data from a .csv is broken in cases like the following:
Actual vs expected output:
If the values are numbers, then it is inferred correctly:
If the column name is 'y', then it is also inferred as expected:
So it's very sensitive.
The text was updated successfully, but these errors were encountered: