Bill Janssen schrieb: >> 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. > > No problem. But I think it's still a bug -- the "spec" (where is it?) > should say what we want. I'll file an issue on it.
I think "the spec" would be the socket API. For sockets, that is POSIX. According to http://www.opengroup.org/pubs/online/7908799/xns/getsockname.html the result is unspecified if the socket has not been bound to a local name. However, Windows does not implement POSIX here; instead, it implements WinSock, which specifies that WSAEINVAL is returned. Regards, Martin _______________________________________________ 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
