This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients lemburg, vstinner
Date 2020-10-26.17:39:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On 26.10.2020 18:05, STINNER Victor wrote:
> By the way, Unicode 3.2 was released in 2002: 18 years ago. I don't think that it's still relevant in 2020 to keep backward compatibility with Unicode 3.2. I propose to deprecate unicodedata.ucd_3_2_0 and deprecate the unicodedate.UCD type. In Python 3.12, we will be able to remove a lot of code, and simplify the code a lot.

The version 3.2.0 is needed for IDNA compatibility:

IDNA 2003:
requires Unicode 3.2 mappings

IDNA 2008: et al.
requires Unicode 5.2+ mappings

Python only supports IDNA 2003 AFAIK and the ucs_3_2_0 tag was added
by Martin von Löwis to support it even after moving forward to more
recent Unicode versions.

IDNA 2008 seems to have mechanisms to also work for Unicode versions
later than 5.2, but I don't know the details. See this TR for details
on how IDNA compatibility is handled:

All that said, it may actually be better to deprecate IDNA 2003 support
first and direct people to:

or incorporate this into the stdlib instead of IDNA 2003. The special
tag can then be dropped.

Marc-Andre Lemburg

Professional Python Services directly from the Experts (#1, Oct 26 2020)
>>> Python Projects, Coaching and Support ...
>>> Python Product Development ...

::: We implement business ideas - efficiently in both time and costs ::: Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
Date User Action Args
2020-10-26 17:39:07lemburgsetrecipients: + lemburg, vstinner
2020-10-26 17:39:07lemburglinkissue42157 messages
2020-10-26 17:39:07lemburgcreate