From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 26 Apr 2021 19:45:45 +0000 (-0700) Subject: bpo-17305: Link to the third-party idna package. (GH-25208) (#25211) X-Git-Tag: v3.8.10~24 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2760a6711b0f510afbd09b19949bee786e098af9;p=thirdparty%2FPython%2Fcpython.git bpo-17305: Link to the third-party idna package. (GH-25208) (#25211) 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 1d023e374cf96d143b065242131ddc9b889f9a1e) Co-authored-by: Gregory P. Smith --- diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst index 992672e806f3..f09b0e1abdc4 100644 --- a/Doc/library/codecs.rst +++ b/Doc/library/codecs.rst @@ -1413,6 +1413,9 @@ Applications) and :rfc:`3492` (Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)). It builds upon the ``punycode`` encoding and :mod:`stringprep`. +If you need the IDNA 2008 standard from :rfc:`5891` and :rfc:`5895`, use the +third-party `idna module _`. + These RFCs together define a protocol to support non-ASCII characters in domain names. A domain name containing non-ASCII characters (such as ``www.Alliancefrançaise.nu``) is converted into an ASCII-compatible encoding