[issue32958] socket module calls with long host names can fail with idna codec error

Gregory P. Smith added the comment: ablack: the basic auth username:password@ part of the string is not part of a hostname. What code are you seeing that is trying to send that to a name resolver rather than stripping the obviously private info up through the @ sign? -- nosy:

[issue32958] socket module calls with long host names can fail with idna codec error

Ben Darnell added the comment: [I'm coming here from https://github.com/tornadoweb/tornado/pull/3010) UnicodeError is a subclass of ValueError, so I don't see what value that change would provide. The thing that's surprising to me is that it's not a `socket.herror` (or `gaierror` for

[issue32958] socket module calls with long host names can fail with idna codec error

Alex Vandiver added the comment: It seems reasonable to fail on hostnames that are too long -- but it feels like the weirdness is that it is categorized as a UnicodeError, and not as, say, a ValueError. Would a re-categorization as ValueError seem like a reasonable adjustment here?

[issue32958] socket module calls with long host names can fail with idna codec error

Change by -- : -- nosy: +midopa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32958] socket module calls with long host names can fail with idna codec error

Aaron Black added the comment: joseph.hackman I don't think that the 63 character limit on a label is the problem specifically, merely it's application. The crux of my issue was that credentials passed with the url in a basic-authy fashion (as some services require) count against the

[issue32958] socket module calls with long host names can fail with idna codec error

Joseph Hackman added the comment: According to the DNS standard, hostnames with more than 63 characters per label (the sections between .) are not allowed [https://tools.ietf.org/html/rfc1035#section-2.3.1]. That said, enforcing that at the codec level might be the wrong choice. I threw

[issue32958] socket module calls with long host names can fail with idna codec error

Steve Bowman added the comment: When will this issue be fixed? Thanks! -- nosy: +sdbowman ___ Python tracker ___ ___

[issue32958] socket module calls with long host names can fail with idna codec error

Change by Ned Deily : -- nosy: -ned.deily ___ Python tracker ___ ___ Python-bugs-list

[issue32958] socket module calls with long host names can fail with idna codec error

Change by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___

[issue32958] socket module calls with long host names can fail with idna codec error

Matt Eaton added the comment: Using Ubuntu 16.04 with the 3.6.0 tag I was also able to reproduce the same error reported: import socket h = "0123456789012345678901234567890123456789012345678901234567890123.example.com" socket.gethostbyname(h) Traceback (most recent

[issue32958] socket module calls with long host names can fail with idna codec error

Aaron Black added the comment: Just to be clear, I don't know if the socket needs to support 64 character long host name sections, so here's an example url that is at the root of my problem that I'm pretty sure it should support: >>> import socket >>> h = >>>

[issue32958] socket module calls with long host names can fail with idna codec error

Ned Deily added the comment: Thanks for the report. The behavior you see can be further isolated to socket.gethostbyname: >>> import socket >>> h = >>> "0123456789012345678901234567890123456789012345678901234567890123.example.com" >>> socket.gethostbyname(h) Traceback (most