Repository navigation
gh-158166: Make ElementTree ParseError messages strings - #158168
serhiy-storchaka merged 6 commits into
Conversation
|
As it has been almost 1 month, following the devguide, gentle ping 😉 For the record this exact fixed has been merged and released in the latest PyPy (8.0.1), and caused an issue for rich exception rendering. |
serhiy-storchaka
left a comment
There was a problem hiding this comment.
LGTM, but could you please reword the NEWS entry?
|
Thanks @alexprengere for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
|
Sorry, @alexprengere and @serhiy-storchaka, I could not cleanly backport this to Please backport manually with cherry_picker, see the devguide for more information. |
|
GH-161885 is a backport of this pull request to the 3.14 branch. |
|
GH-161891 is a backport of this pull request to the 3.15 branch. |
|
@serhiy-storchaka I tried to use |
This fixes issue #158166. We now always cast
ParseErrorfirst argument to astr, like what is already done in_elementtree.c.