Skip to content

Multicharacter delimiters + non-UTF8 encoding doesn't work correctly in parsers #3404

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

Closed
wesm opened this issue Apr 19, 2013 · 2 comments
Closed
Labels
Bug IO CSV read_csv, to_csv IO Data IO issues that don't fit into a more specific label Unicode Unicode strings
Milestone

Comments

@wesm
Copy link
Member

wesm commented Apr 19, 2013

The new C parser handles user-specified encoding properly. The Python parser not so much (I think it may only be an issue when regular-expression parsing is used).

@gfyoung
Copy link
Member

gfyoung commented Jul 26, 2016

@jreback : is it me, or is this no longer an issue? The common.py tests have several encoding ones.

@jorisvandenbossche
Copy link
Member

But I don't see directly any test with the combination of an encoding and a multi-character sep? (so maybe we should add a test for that?)

gfyoung added a commit to forking-repos/pandas that referenced this issue Jul 28, 2016
@jreback jreback modified the milestones: 0.19.0, Someday Jul 28, 2016
jreback pushed a commit that referenced this issue Jul 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug IO CSV read_csv, to_csv IO Data IO issues that don't fit into a more specific label Unicode Unicode strings
Projects
None yet
Development

No branches or pull requests

4 participants