Message111985
"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. |
|
Date |
User |
Action |
Args |
2010-07-29 18:28:21 | baikie | set | recipients:
+ baikie, lemburg, loewis, vstinner, ezio.melotti |
2010-07-29 18:28:21 | baikie | set | messageid: <1280428101.51.0.889708401133.issue9377@psf.upfronthosting.co.za> |
2010-07-29 18:28:19 | baikie | link | issue9377 messages |
2010-07-29 18:28:19 | baikie | create | |
|