Skip to content

bpo-30736: upgrade to Unicode 10.0 #2344

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 23, 2017
Merged

bpo-30736: upgrade to Unicode 10.0 #2344

merged 1 commit into from
Jun 23, 2017

Conversation

benjaminp
Copy link
Contributor

Straightforward. While we're at it, though, strip trailing whitespace from generated tables.

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are links to Unicode 8.0 in Doc/reference/lexical_analysis.rst and Doc/library/stdtypes.rst. Shouldn't they be updated too?

unicodedata
-----------

The internal database has been upgraded to use Unicode 10.0.0. (Contributed by
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a link as in whatsnew/3.6.rst?

@serhiy-storchaka
Copy link
Member

While we're at it, though, strip trailing whitespace from generated tables.

Always wanted to do this.

@serhiy-storchaka
Copy link
Member

As for the CI failure see bpo-29887.

Straightforward. While we're at it, though, strip trailing whitespace from generated tables.
@benjaminp
Copy link
Contributor Author

Yes, I'm glad it fails now.

@benjaminp benjaminp merged commit 279a962 into master Jun 23, 2017
@benjaminp benjaminp deleted the benjamin-uni-10 branch June 23, 2017 05:31
@srl295
Copy link

srl295 commented Aug 3, 2017

Rando here. Does this fetch directly from unicode.org? because dodo/node-unicodetable#16 (comment)

@benjaminp
Copy link
Contributor Author

benjaminp commented Aug 4, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants