This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients amaury.forgeotdarc, davidfraser, dmalcolm, joshbressers, pitrou, scott.dial, vstinner
Date 2010-12-20.18:40:57
SpamBayes Score 2.90194e-06
Marked as misclassified No
Message-id <1292870454.3737.61.camel@localhost.localdomain>
In-reply-to <>
> > The problem is to detect that stderr file descriptor changes (eg. closed, 
> > duplicated, reopened, etc.). I don't think that it's possible to detect such 
> > changes (with a portable function).
> When I said that, I hadn't fully investigated the intricacies of the io
> types. I was unaware that you could assign to "sys.stderr.buffer.raw"
> and change out the target fd. I assumed a BufferedWriter could not have
> the target stream changed out from beneath it.

AFAICT, this is not deliberate (not documented, and not tested for). It
should probably be fixed, actually, because there's no code that I know
of that ensures it does something meaningful.
Date User Action Args
2010-12-20 18:40:58pitrousetrecipients: + pitrou, amaury.forgeotdarc, davidfraser, scott.dial, vstinner, dmalcolm, joshbressers
2010-12-20 18:40:57pitroulinkissue8863 messages
2010-12-20 18:40:57pitroucreate