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 peter.otten
Recipients andriusl, peter.otten, vinay.sajip, xtreak
Date 2019-03-06.09:18:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551863919.64.0.862520048192.issue36193@roundup.psfhosted.org>
In-reply-to
Content
[Andrius]
> So it is not possible to consistently manage stderr when it involves > logging library without explicitly "manage" it?

That's what I think, at least from within a script. To me redirect_xxx() always looked like a workaround to have old code write to a destination that was unforeseen in the initial design. I prefer

dump_stuff(dest)

to

with redirect_stdout(dest):
   dump_stuff()

That said -- do you have a suggestion how the logging library could be adapted to work smoothly with redirect_xxx()?

(A compelling use case would also be nice, but note that I'm not the one who makes the decisions.)
History
Date User Action Args
2019-03-06 09:18:39peter.ottensetrecipients: + peter.otten, vinay.sajip, xtreak, andriusl
2019-03-06 09:18:39peter.ottensetmessageid: <1551863919.64.0.862520048192.issue36193@roundup.psfhosted.org>
2019-03-06 09:18:39peter.ottenlinkissue36193 messages
2019-03-06 09:18:39peter.ottencreate