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-08-27.19:13:03
SpamBayes Score 2.2763466e-08
Marked as misclassified No
Message-id <>
In-reply-to <>
> > 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).

That's bad if it's on the public Internet, but it's not an
error.  The OS is returning the name by which it knows the host.

If you look at POSIX, you'll see that what getaddrinfo() and
getnameinfo() look up and return is referred to as a "node name",
which can be an address string or a "descriptive name", and that
if used with Internet address families, descriptive names
"include" host names.  It doesn't say that the string can only be
an address string or a hostname (RFC 1123 compliant or

> > 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).

It's not reasonable when addressed to a customer who might go
elsewhere.  And I still don't see a technical reason for making
such a demand.  Python 2.x seems to work just fine using 8-bit
Date User Action Args
2010-08-27 19:13:19baikiesetrecipients: + baikie, lemburg, loewis, vstinner, ezio.melotti
2010-08-27 19:13:04baikielinkissue9377 messages
2010-08-27 19:13:03baikiecreate