Add support for Unicode 15.1 #62
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The possibility for 'narrow' builds of CPython went away with Python 3.3
|
@anthrotype Could you tag a new release? |
|
Yes, I will do tomorrow, thanks for the reminder. @SnoopJ is there anything else you'd like to get in before the next release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changeset updates
unicodedata2to add Unicode 15.1 support, following the analogous changes upstream. There are also some housekeeping changes: synchronizing the test suite and dropping dead code that used to support narrow builds of CPython. The overall result of this housekeeping is that the expectation checksum now follows the value in the upstream test suite.This changeset also adds Python 3.12 to the
toxconfiguration in anticipation of the coming release.Closes #60, #61