Release 14.0.0

[Harmon758]

I'm going to be working on the next release, 14.0.0. This is what I anticipate being done:

• Correct 13.0.0-2 tag
  • The 13.0.0-2 tag pointed to c71c98e, a commit that's part of setup.py: bump version to 13.0.0-2 #38 and not on the master branch of this repository
  • It now points to 8b91235, the equivalent commit that merged setup.py: bump version to 13.0.0-2 #38 into the master branch of this repository
  • I've force-pushed the tag to point to the correct commit
• Add changelog for 13.0.0-2 (Add changelog for 13.0.0-2 #45)
  • This was missing in CHANGELOG.md
• Update references to repository (Update references to repository #46)
  • mikekap -> fonttools (request to move repo under fonttools organization #43)
• Drop support for Python 3.5 (Drop support for Python 3.5 #47)
  • Python 3.5 has been EOL since September 2020
  • PyPI Stats shows the download proportion for Python 3.5 to be virtually 0%
• Drop support for Python 2(.7) (Drop support for Python 2 #48)
  • Python 2(.7) has been EOL since January 2020
  • PyPI Stats shows the download proportion for Python 2.7 to be consistently under 4% and mainly under 1-2%
  • I think it's safe to do this now, with it having been EOL for almost two years and the download proportion being so low
  • It would significantly reduce the maintenance burden and make updating for each Unicode version simpler
  • There's precedent for doing this, with support for EOL Python 3.x versions (and 2.6) being dropped in past releases
  • I think continuing to only support versions of Python that are still maintained and not EOL yet (3.6+ right now) for each release is the best way forward
• Switch from Travis CI to GitHub Actions (move off Travis.org to Github Actions CI #40)
  • Switch from multibuild to cibuildwheel
    • I'm not particularly set on this, but cibuildwheel seems to be easier to set up with GitHub Actions and possibly more readily and regularly maintained/updated, now that it's a PyPA member project
    • It might also be easier to add support for PyPy (Support PyPy? #17) with cibuildwheel
• Add support for Python 3.9
  • Python 3.9 was released October 2020
  • unicodedata2 13.0.0.post2 (13.0.0-2) has been working with Python 3.9 for me, but support for it still needs to be declared and it would be best to build actual wheels for it
• Add support for Python 3.10
  • Python 3.10 was released October 2021
  • unicodedata2 13.0.0.post2 currently fails to install with Python 3.10 for me
• Update to Unicode 14.0
  • Review other relevant commits to CPython since the last unicodedata2 release and consider cherry-picking each one
  • http://blog.unicode.org/2021/09/announcing-unicode-standard-version-140.html
  • https://home.unicode.org/announcing-the-unicode-standard-version-14-0/
  • https://www.unicode.org/versions/Unicode14.0.0/
  • https://bugs.python.org/issue45190
  • closes bpo-45190: Update Unicode data to version 14.0.0. python/cpython#28336 (python/cpython@024fda4)

Feedback is welcome.

[anthrotype]

thanks a lot @Harmon758 for taking this on! It all sounds good to me

continuing to only support versions of Python that are still maintained and not EOL yet (3.6+ right now) for each release is the best way forward

I 100% agree, I think we can drop 2.7 and 3.5, if also @mikekap has no objections.

cibuildwheel seems to be easier to set up with GitHub Actions and possibly more readily and regularly maintained/updated

👍

[mikekap]

I have no objections for dropping 2.x support. It's way past due and it's a pragmatic technical decision to boot.

That said, if I remember well, this package was actually originally created to bring new unicode tables to py2. Py3 support for newer tables was actually added after the first release. That's what the 2 in the name originally meant. No need to change anything but just a bit of fun trivia.

[anthrotype]

Switch from Travis CI to GitHub Actions

@Harmon758 I recently did this for py-zopfli, you may want to take a look at
fonttools/py-zopfli#12 and fonttools/py-zopfli@a3473c7

[catap]

I'd love to link my PR: #49 whcih allow to build and install unicodedata2 under Python 3.10

[anthrotype]

thanks @catap! I merged the PR and marked the py310 support in the todo list checkboxes

[catap]

@anthrotype FYI: I'm adding support of py310 in macports here: macports/macports-ports#13005

You may find backported version for my PR for last release.

I don't think that you need to merge it, but link here seems a good place, because it allow to grab ready to use patch for someone who needed it.

[anthrotype]

@Harmon758 let me know if you think there's anything left before we can make the 14.0.0 release, thanks!

[khaledhosny]

Can we have the release and fix any issues when they arise?

[anthrotype]

https://github.com/fonttools/unicodedata2/releases/tag/14.0.0 - thanks all!