Martin v. Löwis <mar...@v.loewis.de> added the comment: > I don't see how a name resolution API returning non-ASCII bytes > would indicate an error.
It's in violation of RFC 952 (slightly relaxed by RFC 1123). > But to be more explicit, that's like saying "if it hurts, get > your sysadmin to reconfigure the company network". Which I consider perfectly reasonable. The sysadmin should have known (and, in practice, *always* knows) not to do that in the first place (the larger the company, the more cautious the sysadmin). ---------- title: socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names -> socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9377> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
