-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Allow backslashreplace error handler to be used on input #66482
Comments
In the discussion on bpo-18814, Antoine pointed out that in a Python 3 world, using backslashescape during decoding actually makes sense - it lets you accurately report arbitrary bytes in the sequence, without needing surrogateescape or surrogatepass to be used when encoding later. |
Here is a patch. |
Could you make a review Nick to get this feature in the first alpha. |
+1 from me for merging, although I suspect you'll need to adjust the codecs.rst changes first. |
New changeset dd8a03e98158 by Serhiy Storchaka in branch 'default': |
Looks like the buildbots aren't happy with this change. |
Yes, I see. The patch exposed existing bug in decoding error handing. See bpo-23321 for this. |
New changeset 1e8937861ee3 by Victor Stinner in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: