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 baikie
Recipients baikie, ezio.melotti, lemburg, loewis, vstinner
Date 2010-07-29.18:28:18
SpamBayes Score 0.25691783
Marked as misclassified No
Message-id <1280428101.51.0.889708401133.issue9377@psf.upfronthosting.co.za>
In-reply-to
Content
"Leaving IDNA ASCII-compatible encodings in ASCII form" is just preserving the existing behaviour (not doing IDNA decoding).  See

http://tools.ietf.org/html/rfc3490

and the docs for codecs -> encodings.idna ("xn--lzg" in the example is the ASCII-compatible encoding of "€", so if you look up that IP address, "xn--lzg" is returned with or without the patch).

I'll look into your other comments.  In the meantime, I've got one more patch, as the decoding of the nodename field in os.uname() also needs to be changed to match the other hostname-returning functions.  This patch changes it to ASCII/surrogateescape, with the usual PEP 383 decoding for the other fields.
History
Date User Action Args
2010-07-29 18:28:21baikiesetrecipients: + baikie, lemburg, loewis, vstinner, ezio.melotti
2010-07-29 18:28:21baikiesetmessageid: <1280428101.51.0.889708401133.issue9377@psf.upfronthosting.co.za>
2010-07-29 18:28:19baikielinkissue9377 messages
2010-07-29 18:28:19baikiecreate