DOC: Document how encoding errors are handled #39492
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
thanks @twoertwein |
This comment has been minimized.
This comment has been minimized.
Contributor
|
@meeseeksdev backport 1.2.x |
This comment has been minimized.
This comment has been minimized.
simonjayhawkins
pushed a commit
to simonjayhawkins/pandas
that referenced
this pull request
Feb 2, 2021
simonjayhawkins
added a commit
that referenced
this pull request
Feb 2, 2021
…9552) Co-authored-by: Torsten Wörtwein <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
xref #39450
This should probably go in 1.2.2.
<1.2.0:
engine=candengine=pythonhandled encoding errors differently whenencoding=None(python: "replace", c: "strict"). Theengine=cfurther supported to ignore lines (skiprows) with encoding errors iffencoding=None.1.2.0 (shared file opening code between
engine=candengine=python): both engine mistakenly used "strict" whenencoding=None.engine=c+encoding=Nonecan no longer skip encoding errors.1.2.1: both engine use "replace" when
encoding=None. Both engines can ignore encoding errors in skipped rows iffencoding=None.Option for 1.3: default to "strict" but expose
errorsinread_csv(and other read calls that might need it)?