FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

bpo-37388: Don't check encoding/errors during finalization by vstinner · Pull Request #19409 · python/cpython · GitHub

Repository navigation

bpo-37388: Don't check encoding/errors during finalization - #19409

Merged
vstinner merged 1 commit into
python:masterfrom
vstinner:unicode_check_encoding_errors
Apr 7, 2020
Merged

vstinner merged 1 commit into
python:masterfrom
vstinner:unicode_check_encoding_errors

Conversation

vstinner commented Apr 7, 2020 •
edited by bedevere-bot
Loading

Copy link
Copy Markdown
Member

str.encode() and str.decode() no longer check the encoding and errors
in development mode or in debug mode during Python finalization. The
codecs machinery can no longer work on very late calls to
str.encode() and str.decode().

This change should help to call _PyObject_Dump() to debug during late
Python finalization.

https://bugs.python.org/issue37388

str.encode() and str.decode() no longer check the encoding and errors
in development mode or in debug mode during Python finalization. The
codecs machinery can no longer work on very late calls to
str.encode() and str.decode().

This change should help to call _PyObject_Dump() to debug during late
Python finalization.
vstinner merged commit d8acf0d into python:master Apr 7, 2020
vstinner deleted the unicode_check_encoding_errors branch April 7, 2020 14:07
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
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

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL