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 David.Edelsohn
Recipients David.Edelsohn
Date 2013-06-26.15:37:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372261030.27.0.471709034157.issue18308@psf.upfronthosting.co.za>
In-reply-to
Content
The recvmsg tests in test_socket.py check that the address returned by recvmsg matches the original address to which the socket was bound. For IPv6, sockaddr includes sin6_scope_id, in addition to the address and port.

The test connects to host "::1", which is loopback, but is an under-specified address because the link scope is left ambiguous.

The scope_id in the original bind call defaults to "0", which represents an ambiguous scoped address and allows the IPV6 protocol and implementation to choose the interface or site identifier.  The recvmsg call returns the actual scope_id.

The test incorrectly checks that the full sockaddr matches. sin6_scope_id may not match for IPv6 addresses.  This generates bogus failures on AIX.

(Microsoft has a good description about scope_id:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms739166%28v=vs.85%29.aspx)
History
Date User Action Args
2013-06-26 15:37:10David.Edelsohnsetrecipients: + David.Edelsohn
2013-06-26 15:37:10David.Edelsohnsetmessageid: <1372261030.27.0.471709034157.issue18308@psf.upfronthosting.co.za>
2013-06-26 15:37:10David.Edelsohnlinkissue18308 messages
2013-06-26 15:37:09David.Edelsohncreate