Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
gh-109559: Updateunicodedata for Unicode 15.1#109560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes from1 commit
21e297c122a7326d5238ecd9cbf5818a36c24088ca110c552d8d9f9827b1c13af730eb0db692044f6770File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
- Loading branch information
Uh oh!
There was an error while loading.Please reload this page.
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1106,11 +1106,15 @@ def __init__(self, version, cjk_check=True): | ||
| table[i].east_asian_width = widths[i] | ||
| self.widths = widths | ||
| for char, (propname, *propinfo) in UcdFile(DERIVED_CORE_PROPERTIES, version).expanded(): | ||
| if propinfo: | ||
| # this is not a binary property, ignore it | ||
| continue | ||
Comment on lines +1109 to +1112 ContributorAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. All the properties defined in As of Unicode 15.1, this file also includes definitions that use the With this change, the loop skips over any non-binary properties, since we have nothing to do with them. Contributor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. It seems like it would be safer to explicitly ignore ContributorAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Is there a particular failure mode you have in mind? My rationale here was that the current internalized DB only cares about binary properties in this file, but in practice any of theproperty types enumerated by UAX#44 could appear in a future revision. I'm not strongly opposed to ignoring the specific property that breaks the tool against the current revision, but my rationale was that it seems safer to prevent this class of failure in the future if/when additional non-binary properties are added. | ||
| if table[char]: | ||
| # Some properties (e.g. Default_Ignorable_Code_Point) | ||
| # apply to unassigned code points; ignore them | ||
| table[char].binary_properties.add(propname) | ||
| for char_range, value in UcdFile(LINE_BREAK, version): | ||
| if value not in MANDATORY_LINE_BREAKS: | ||