On Feb 18, 2008 4:12 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > > Is it possible that CPython's socket.close method won't actually close > the socket while there's still a makefile'd file attacked to the > underlying OS socket? And that IronPython's will? Because that's the > only explanation I can come up with.
It is and it will. CPython basically dups the socket handle when you call makefile, while IronPython does not. That's the cause of this bug. By the way, the docstring for the IronPython socket class claims that makefile isn't implemented. This is apparently only half-true. :P -- Curt Hagenlocher [EMAIL PROTECTED] _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
