gh-142224: makeunicodedata.py: parse default bidi values - #144815
Conversation
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I was going to work on this issue next week, but you saved my time. Thank you.
# Conflicts: # Lib/test/test_unicodedata.py # Tools/unicode/makeunicodedata.py
|
Sorry, I don't have time for a true review. From a casual look, this LGTM, though. |
|
Thanks @StanFromIreland for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Thanks @StanFromIreland for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
Sorry, @StanFromIreland and @serhiy-storchaka, I could not cleanly backport this to |
|
Sorry, @StanFromIreland and @serhiy-storchaka, I could not cleanly backport this to |
|
I am not sure if it is worth to backport this. |
No worries, thanks for the reviews.
Yes, I would think it is an uncommon issue. |
… 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 <seth@python.org> Co-authored-by: Stan Ulbrych <89152624+stanfromireland@users.noreply.github.com> Co-authored-by: Petr Viktorin <encukou@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.