➜

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 vitaly.krug
Recipients paul.moore, steve.dower, tim.golden, vitaly.krug, zach.ware
Date 2018-04-02.18:57:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522695462.69.0.467229070634.issue33206@psf.upfronthosting.co.za>
In-reply-to
Content 
Zachary, thank you for noticing that Twisted is involved. inet_pton definitely exists on Windows 2.7.14, but it turns out that Twisted monkey-patches it if `socket.inet_pton(socket.AF_INET6, "::")` fails.

Aha! - but this suggests that Window's Python 2.7.14 implementation of `socket.inet_pton()` has a bug in that it fails to recognize '::' as the the IPv6 unspecified address 0:0:0:0:0:0:0:0, so `socket.inet_pton(socket.AF_INET6, "::")` fails. I wonder if this exists on Windows Python3 implementations?
History
Date User Action Args
2018-04-02 18:57:42vitaly.krugsetrecipients: + vitaly.krug, paul.moore, tim.golden, zach.ware, steve.dower
2018-04-02 18:57:42vitaly.krugsetmessageid: <1522695462.69.0.467229070634.issue33206@psf.upfronthosting.co.za>
2018-04-02 18:57:42vitaly.kruglinkissue33206 messages
2018-04-02 18:57:42vitaly.krugcreate