> 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') Actually, I think this is a bug in the Windows implementation of the socket interface. The question is, what should s.getsockname() return (or throw) if called on an unbound socket instance? Unix decided one way, and Windows another (and not a particularly good way). I'll post an issue to the tracker. Bill
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4