Yes - this is true. socket.makefile (and one other from memory) require the
functionality of a socket handle being equal to a file handle (ie, need to
be able to pass a socket handle to dup())
This is infact true for NT 3.5, but I am reluctant to make this change, as
it certainly is not true for NT 3.1, Win32s, and possibly not true for Win
'95/96.
We did come up with a technique that would do something like the following:
* provide a new "makefile" method.
* return a new object type (with a reference to the original socket) and
"simulate" read/write type calls (ie, make the new object look like a file
object)
(Sorry, but I cant remember the details we worked out on this, but from
memory ftplib et al have similar problems....)
As usual, all contributions, enhancements, workarounds, fixes, hacks etc all
welcomed!
Regards,
Mark (MHammond@cmutual.com.au)