Looking at the buildbots today, Windows is still unhappy. It seems to
have gotten further, though.
The problematic test is this one:
File "C:\buildbot_py25\trunk.mcintyre-windows\build\lib\test\test_ssl.py",
line 77, in testSSLconnect
s.connect(("pop.gmail.com", 995))
File "C:\buildbot_py25\trunk.mcintyre-windows\build\lib\ssl.py", line 170, in
connect
if self._sslobj or (self.getsockname()[1] != 0):
File "<string>", line 1, in getsockname
error: (10022, 'Invalid argument')
Looks like a valid complaint, actually. It should probably read
if self._sslobj or (int(getnameinfo(self.getsockname(), 0)[1]) != 0):
where "getnameinfo" is from the socket module. We're trying to see if
the socket has been bound or connected already.
I'm loath to generate a patch till I actually try this on a Windows
machine. So I'm going to try that this afternoon, and generate a new
patch for you.
Bill
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
