[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-04-03 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16208 ___ ___

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-24 Thread Ralf Schmitt
Ralf Schmitt added the comment: Marc, I think you'll have to bring this up on the mailing list if you want to have anything changed. The developers on the nosy list have already closed this as wont fix. They don't care anymore. -- ___ Python

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-22 Thread Marc Schlaich
Marc Schlaich added the comment: I agree with schmir, this is really unexpected behavior. At least it should be fixed in the documentation. The doc currently says you get a 4-tuple for IPv6, which is just wrong in this case. Prominent library stumbled about this issue is Tornado

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread STINNER Victor
STINNER Victor added the comment: The switch --disable-ipv6 is supported and works as intended. It is not the intention of the switch to disable lookups. Instead, it disables support for IPv6 sockets. I just think that this definition is not exact. Do you seriously expect IPv6 to work

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Ralf Schmitt
Ralf Schmitt added the comment: socket getaddrinfo returns garbage: socket.getaddrinfo(python.org, 80) [(2, 1, 6, '', ('82.94.164.162', 80)), (2, 2, 17, '', ('82.94.164.162', 80)), (2, 3, 0, '', ('82.94.164.162', 80)), (10, 1, 6, '', (10, '\x00P\x00\x00\x00\x00 \x01\x08\x88 \x00\x00\r')),

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread STINNER Victor
STINNER Victor added the comment: socket.getaddrinfo(python.org, 80) This is a different issue: it's #7735. Do you really think that this is not a bug? #7735 is a bug but it was decided that it will not be fixed. You may reopen #7735 if you disagree. --

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Martin v. Löwis added the comment: The data returned is not bogus; this is the correct result. If the system's getaddrinfo returns an unsupported address family, Python returns a bytes object (the system's sockaddr buffer) to the application. This should be documented, though (either in the

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Ralf Schmitt
Ralf Schmitt added the comment: Given the fact that the bytes object is rather surprising and probaby useless for the caller I wouldn't call this a correct result. (sorry, I lost too much time on this issue, I had to put another comment here). --

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Martin v. Löwis added the comment: It's not at all useless: it enables the application to bypass limitations in Python, i.e. process the sockaddr on its own (very much in the same way as you have to do for ioctl/fcntl). Whether it's surprising or not depends on what you expected to happen.

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Ralf Schmitt
Ralf Schmitt added the comment: The TypeError error happened when using gevent. I've already written in that other issue that this information was wrong and I get a bad family error. Sorry, about that. But this also demonstrates my point here. The Type error was raised exactly because the

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Martin v. Löwis added the comment: schmir: your information on msi support is probably outdated; pypi.python.org does support MSI files, see for example http://pypi.python.org/pypi/Twisted/12.3.0 -- ___ Python tracker rep...@bugs.python.org

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Changes by Martin v. Löwis mar...@v.loewis.de: -- Removed message: http://bugs.python.org/msg178791 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16208 ___

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Martin v. Löwis added the comment: (sorry, wrong issue) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16208 ___ ___ Python-bugs-list mailing

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2013-01-01 Thread Martin v . Löwis
Changes by Martin v. Löwis mar...@v.loewis.de: -- Removed message: http://bugs.python.org/msg178789 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16208 ___

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2012-10-12 Thread Ralf Schmitt
Changes by Ralf Schmitt python-b...@systemexit.de: -- nosy: schmir priority: normal severity: normal status: open title: getaddrinfo returns wrong results if IPv6 is disabled ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16208

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2012-10-12 Thread Ralf Schmitt
New submission from Ralf Schmitt: I'm running the following code on python 2.7.3 on a 64 bit linux. import socket print has_ipv6, socket.has_ipv6 res = socket.getaddrinfo(python.org, 80, socket.AF_INET6, socket.SOCK_STREAM) print python.org is, res With IPv6 enabled, I get the following

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2012-10-12 Thread STINNER Victor
STINNER Victor added the comment: getaddrinfo returns wrong results if IPv6 is disabled If IPv6 support is disabled, Python is unable to decode an IPv6 address. So don't ask for IPv6 addresses if you disabled IPv6 support. I don't understand this issue. -- nosy: +haypo

[issue16208] getaddrinfo returns wrong results if IPv6 is disabled

2012-10-12 Thread Ralf Schmitt
Ralf Schmitt added the comment: Thanks for looking at this. loewis told me in http://bugs.python.org/issue7735#msg172726 the following: The switch --disable-ipv6 is supported and works as intended. It is not the intention of the switch to disable lookups. Instead, it disables support