Re: [Python-3000] close() on open(fd, closefd=False)

I see no problem in fixing this in 3.0 and 2.6.1. The current behavior is a bug and I see no reason to expect that users would depend on it. Sure, it might occasionally mask a bug elsewhere in their code -- but given how esoteric this whole issue is I think its fine to consider this simply a bug an

Re: [Python-3000] close() on open(fd, closefd=False)

Note that the whole httplib uses this behavior -- issue 1348. Bill Guido van Rossum <[EMAIL PROTECTED]> wrote: > I see no problem in fixing this in 3.0 and 2.6.1. The current behavior > is a bug and I see no reason to expect that users would depend on it. > Sure, it might occasionally mask a bug

Re: [Python-3000] close() on open(fd, closefd=False)

Are you sure? I thought that was different -- httplib depends on the reference count semantics of socket objects. The closefd behavior that Christian is describing here is part of the (new in 2.6 and 3.0) io.py module. On Mon, Nov 3, 2008 at 7:25 PM, Bill Janssen <[EMAIL PROTECTED]> wrote: > Note