-
Notifications
You must be signed in to change notification settings - Fork 136
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
Improve error message in case of misidentification of dialect (ValueError: Can't decode base64) #218
Comments
The issue is that |
I'm not very into building more complexity in dialect guessing (297a992), I would actually prefer to be required to explicitly inform the dialect instead. What do you guys think? Besides, I think that the boundaries between field type guessing and dialect guessing doesn't look clear, but the error message format as in d20c90d is a very good step towards this separation. 👍 |
👍 , feel free to close it. |
When I run the code bellow, I got the error
ValueError: Can't decode base64
because rows use the first line to discover the csv dialect, but the text present at the following line breaks the expectation.The problem is solved if you add the dialect explicitly:
but would be very nice to have a error message that points us to the right direction, like talking about dialects or just by telling the row and field where error happened.
The text was updated successfully, but these errors were encountered: