Antoine Pitrou <pit...@free.fr> added the comment: > > 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. ---------- title: Display Python backtrace on SIGSEGV, SIGFPE and fatal error -> Display Python backtrace on SIGSEGV, SIGFPE and fatal error _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8863> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
