Re: [Python-3000] socket makefile bug

2007-08-03 Thread Guido van Rossum
On 8/3/07, Jeremy Hylton <[EMAIL PROTECTED]> wrote: > On 8/3/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > The docs are out of date, we don't dup() any more (that was needed > > only because we were using fdopen()). But what *should* happen is that > > when you close the file object the socke

Re: [Python-3000] socket makefile bug

2007-08-03 Thread Jeremy Hylton
On 8/3/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > The docs are out of date, we don't dup() any more (that was needed > only because we were using fdopen()). But what *should* happen is that > when you close the file object the socket is still open. The socket > wrapper's close() method shoul

Re: [Python-3000] socket makefile bug

2007-08-03 Thread Guido van Rossum
The docs are out of date, we don't dup() any more (that was needed only because we were using fdopen()). But what *should* happen is that when you close the file object the socket is still open. The socket wrapper's close() method should be fixed. I can look into that later today. On 8/3/07, Jerem

[Python-3000] socket makefile bug

2007-08-03 Thread Jeremy Hylton
I'm looking into httplib problems on the struni branch. One unexpected problem is that socket.makefile() is not behaving correctly. The docs say "The file object references a dup()ped version of the socket file descriptor, so the file object and socket object may be closed or garbage-collected ind