| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…onGH-24843) Python no longer fails at startup with a fatal error if a command line argument contains an invalid Unicode character. The Py_DecodeLocale() function now escapes byte sequences which would be decoded as Unicode characters outside the [U+0000; U+10ffff] range. Use MAX_UNICODE constant in unicodeobject.c. (cherry picked from commit 9976834) Co-authored-by: Victor Stinner <vstinner@python.org>
|
@vstinner: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, good bot.
Sorry, something went wrong.
This should allow us to drop our custom argv (bytes) handling since the underlying issue https://sourceware.org/bugzilla/show_bug.cgi?id=2373 appears to have been fixed upstream and then backported all the way to 3.8: 614e836f6e934854c6bbf698d759e5cde607a629 bpo-35883: Py_DecodeLocale() escapes invalid Unicode characters (GH-24843) python/cpython#24906 We can also count on having Py_BytesMain, and gain access to assignment expressions and positional-only parameters. Version 3.8's been available since 2019, and 3.7 is well past its upstream EOL. Signed-off-by: Rob Browning <rlb@defaultvalue.org> Tested-by: Rob Browning <rlb@defaultvalue.org>
| Back | FazBrowse Home | New Git URL |
Python no longer fails at startup with a fatal error if a command
line argument contains an invalid Unicode character.
The Py_DecodeLocale() function now escapes byte sequences which would
be decoded as Unicode characters outside the [U+0000; U+10ffff]
range.
Use MAX_UNICODE constant in unicodeobject.c.
(cherry picked from commit 9976834)
Co-authored-by: Victor Stinner vstinner@python.org
https://bugs.python.org/issue35883