[Python-Dev] Other SSL issues in the tracker have been marked

Guido van Rossum guido at python.org
Wed Aug 29 00:40:15 CEST 2007

```On 8/28/07, Bill Janssen <janssen at parc.com> wrote:
> > 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.

Well, that's just what you get with two independent implementations of
a spec. We don't try to hide the differences between the sockets stack
in Unix and Windows -- you'll just have to work around it.

--