➜

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 danielsh
Recipients Evan.Teran, danielsh, giampaolo.rodola, loewis, pitrou, schmir, vstinner
Date 2012-12-31.04:51:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356929496.71.0.884978005104.issue7735@psf.upfronthosting.co.za>
In-reply-to
Content 
Victor, thanks for the summary.  I view things a little differently, so I'll offer my POV:

1. The OPs (Evan and Ralf) build with --disable-ipv6.
2. --disable-ipv6 disables support for IPv6 sockets.  (as per Martin, and AFAIK as per the common meaning of that flag in other configure scripts.)  It does not disable AAAA DNS queries in stdlib DNS client modules.  It does not disable IPv6 support in the 'ipaddress' module.  It does not signify that IPv6 is/isn't supported by libc.  It is orthogonal to whether any interface has IPv6 addresses configured.
3. socket.create_connection() requests IPv6 addresses when Python was built with --disable-ipv6.
4. The OPs claim that (3) is a bug, reasoning that, as create_connection() should not try to connect(2) to IPv6 addresses (per (2)), it's pointless, wasteful, or wrong for it to request them in the first place.
5. Ralf provided a one-line patch for (4):
https://github.com/SiteSupport/gevent/commit/9b1bccffc11455112076189f35023291cf97a2a2

In other words, the issue revolves around configuring Python not to create IPv6 sockets on IPv6-capable systems.

HTH
History
Date User Action Args
2012-12-31 04:51:36danielshsetrecipients: + danielsh, loewis, pitrou, vstinner, giampaolo.rodola, schmir, Evan.Teran
2012-12-31 04:51:36danielshsetmessageid: <1356929496.71.0.884978005104.issue7735@psf.upfronthosting.co.za>
2012-12-31 04:51:36danielshlinkissue7735 messages
2012-12-31 04:51:36danielshcreate