Skip to content
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

Sniffing CSV dialect: an option not the default? #52

Open
rufuspollock opened this issue Jun 12, 2019 · 3 comments
Open

Sniffing CSV dialect: an option not the default? #52

rufuspollock opened this issue Jun 12, 2019 · 3 comments

Comments

@rufuspollock
Copy link
Contributor

Atm we auto-sniff the CSV dialect if it is not provided. This adds complexity (and overhead) to use.

Maybe we could switch to being an option rather than the default.

@anuveyatsu any idea why we started doing this?

@anuveyatsu
Copy link
Member

@rufuspollock we started doing this to support different field delimiters such as semicolon etc.

@rufuspollock
Copy link
Contributor Author

@anuveyatsu makes sense. Do you think it should be optional or not?

@anuveyatsu
Copy link
Member

@rufuspollock I might be wrong but as I know in some countries, e.g., France and Italy ; is used more frequently than , as a field delimiter. I've also seen some sources with tab delimited fields. However, I'm not sure how often they are. I think we should keep it as default right now and wait for an issue from users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants