bpo-17305: Link to the third-party idna package. (GH-25208)

So long as we don't have idna2008 in the standard library, we should at least point people to the third-party solution.
(cherry picked from commit 1d023e374c)

Co-authored-by: Gregory P. Smith <greg@krypto.org>
This commit is contained in:
Miss Islington (bot) 2021-04-06 01:19:15 -07:00 committed by GitHub
parent 028d5286d4
commit c7ccb0ff61
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1414,6 +1414,9 @@ Applications) and :rfc:`3492` (Nameprep: A Stringprep Profile for
Internationalized Domain Names (IDN)). It builds upon the ``punycode`` encoding Internationalized Domain Names (IDN)). It builds upon the ``punycode`` encoding
and :mod:`stringprep`. and :mod:`stringprep`.
If you need the IDNA 2008 standard from :rfc:`5891` and :rfc:`5895`, use the
third-party `idna module <https://pypi.org/project/idna/>_`.
These RFCs together define a protocol to support non-ASCII characters in domain These RFCs together define a protocol to support non-ASCII characters in domain
names. A domain name containing non-ASCII characters (such as names. A domain name containing non-ASCII characters (such as
``www.Alliancefrançaise.nu``) is converted into an ASCII-compatible encoding ``www.Alliancefrançaise.nu``) is converted into an ASCII-compatible encoding