Repository navigation
gh-155292: Don't consider Unicode codepoint attributes outside RFC 3454 - #155293
Conversation
Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. Co-authored-by: Stan Ulbrych <[email protected]>
|
@StanFromIreland @malemburg Now that GHA service has recovered, requesting a review on this PR. |
Co-authored-by: Petr Viktorin <[email protected]>
|
I filed a suggestion as a PR: sethmlarson#2. Otherwise, LGTM -- I didn't find another issue. @malemburg would be the best person to review this, of course. Marc-André, should we wait for you? |
malemburg
left a comment
There was a problem hiding this comment.
I don't have time for a review, but from casual inspection, this looks good to me. Thanks.
|
Thanks for the fix!
OK; let me know if you want to delegate. |
|
Thanks @sethmlarson for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.15. |
|
GH-156017 is a backport of this pull request to the 3.15 branch. |
…RFC 3454 (pythonGH-155293) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]> (cherry picked from commit 7e109d0)
|
GH-156020 is a backport of this pull request to the 3.14 branch. |
… RFC 3454 (GH-155293) (#156017) gh-155292: Don't consider Unicode codepoint attributes outside RFC 3454 (GH-155293) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]>
… RFC 3454 (GH-155293) (GH-156020) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) The cherry-pick needed reworking as GH-144815 wasn't backported to 3.14 and below, so unassigned characters don't have bidi values. Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]>
… RFC 3454 (GH-155293) (GH-156020) (#156930) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) The cherry-pick needed reworking as GH-144815 wasn't backported to 3.14 and below, so unassigned characters don't have bidi values. (cherry picked from commit 1e54caa) Also, add Unicode_3_2_0_FunctionsTest as in the later versions, to make the new test work. Co-authored-by: Seth Larson [email protected] Co-authored-by: Stan Ulbrych [email protected] Co-authored-by: Petr Viktorin [email protected]
… RFC 3454 (GH-155293) (GH-156020) (GH-156922) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) The cherry-pick needed reworking as GH-144815 wasn't backported to 3.14 and below, so unassigned characters don't have bidi values. (cherry picked from commit 1e54caa) Co-authored-by: Petr Viktorin <[email protected]> Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]> --------- Co-authored-by: Petr Viktorin <[email protected]> Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]>
… RFC 3454 (GH-155293) (GH-156020) (#156932) * [3.10] gh-155292: Don't consider Unicode codepoint attributes outside RFC 3454 (GH-155293) (GH-156020) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) The cherry-pick needed reworking as GH-144815 wasn't backported to 3.14 and below, so unassigned characters don't have bidi values. (cherry picked from commit 1e54caa) Co-authored-by: Petr Viktorin <[email protected]> Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]> * Add Unicode_3_2_0_FunctionsTest * Regenerate Unicode data --------- Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]>
… RFC 3454 (GH-155293) (GH-156020) (#156931) * [3.11] gh-155292: Don't consider Unicode codepoint attributes outside RFC 3454 (GH-155293) (GH-156020) Due to a bug, some Unicode codepoint attributes were considered for characters not yet defined in Unicode 3.2.0 or attributes which changed in later Unicode versions. RFC 3454 (StringPrep) requires using Unicode 3.2.0 strictly. (cherry picked from commit 7e109d0) The cherry-pick needed reworking as GH-144815 wasn't backported to 3.14 and below, so unassigned characters don't have bidi values. Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]> Co-authored-by: Petr Viktorin <[email protected]> (cherry picked from commit 1e54caa) * Add Unicode_3_2_0_FunctionsTest * Regenerate Unicode data --------- Co-authored-by: Seth Larson <[email protected]> Co-authored-by: Stan Ulbrych <[email protected]>
Due to a bug, some Unicode codepoint attributes were considered
for characters not yet defined in Unicode 3.2.0 or attributes
which changed in later Unicode versions. RFC 3454 (StringPrep)
requires using Unicode 3.2.0 strictly.
This PR fixes
makeunicodedata.pyand re-runsmkstringprep.pywith the new Unicode database. In the futuremkstringprep.pyshould be run as a part ofmakeunicodedata.py.I'll take on backporting this PR manually, as we'll need to apply the patch and then re-execute
makeunicodedata.pyfor each Python version as each contains a different Unicode version.