ython 2.6.6 (r266:84292, Aug 24 2010, 21:47:18) 
[GCC 4.4.5 20100816 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket, ssl
>>> s = socket.socket()
>>> wrapped = ssl.wrap_socket(s)
>>> wrapped.recv(1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/ssl.py", line 217, in recv
    return socket.recv(self, buflen, flags)
TypeError: 'member_descriptor' object is not callable


What I expected was a more helpful error, like the unwrapped socket gives:

>> s.recv(1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
socket.error: [Errno 107] Transport endpoint is not connected


The full list of affected methods are all the _delegate_methods from socket.py:

_delegate_methods = ("recv", "recvfrom", "recv_into", "recvfrom_into",
                     "send", "sendto")

The cause is that the SSLSocket subclass is trying to upcall to the _socketobject base class, but the base does not have methods for those, just __slots__ for the instance to fill in with bound methods.

Note that 3.x will give you the expected error message:
>>> s = socket.socket()
>>> wrapped = ssl.wrap_socket(s)
>>> wrapped.recv(1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/antoine/py3k/__svn__/Lib/ssl.py", line 292, in recv
    return socket.recv(self, buflen, flags)
socket.error: [Errno 107] Transport endpoint is not connected

Do you have any idea how to solve it for 2.7? Do you want to provide a patch?

Here's a conservative fix for Python 2.7.  It replaces the attempts to call baseclass.method with direct calls to the decorated object (i.e. replace socket.meth(self, ...) with self._sock.meth(...)).

It also corrects a bunch of incorrect arguments being passed to _sock... it's pretty clear this code was not tested.  I've added a test that exercises each SSLSocket method that corresponds to a socket._delegate_method.

A nicer solution is to simply make socket.socket actually be a simple subclass of _socket.socket rather than the weird decorator it is now.  This has already happened on the py3k branch, which is why it doesn't have this bug.

Nice, thank you. I will look at the patch and commit it if everything's fine.

> A nicer solution is to simply make socket.socket actually be a simple
> subclass of _socket.socket rather than the weird decorator it is now. 
> This has already happened on the py3k branch, which is why it doesn't
> have this bug.

Yes, but such a rearchitecting to the socket module is out of question for 2.x, which is in bugfix mode.

> Yes, but such a rearchitecting to the socket module is out of question 
> for 2.x, which is in bugfix mode.

Yes of course, which is why I made the conservative fix instead :)

The recvfrom() signature is wrong (it doesn't take an address argument). Here is an updated patch.

sendto() has a similar problem. socket.sendto() takes (data, flags=0, addr), but SSLSocket.sendto() incorrectly forwards the arguments. Updated patch attached.

Patch committed in r84806.