[issue30526] Allow setting line_buffering on existing TextIOWrapper
Antoine Pitrou
report at bugs.python.org
Thu Jun 1 06:43:08 EDT 2017
Antoine Pitrou added the comment:
Le 01/06/2017 à 12:41, Serhiy Storchaka a écrit :
>
> First at all, I'm not sure that allowing to modify TextIOWrapper settings after creation is a good idea. I would be feeling uncomfortable if the third-party library changed the buffering or encoding settings of passed text stream for its own needs, and this stream is sys.stdout.
Agreed that third-party libraries should not, but we're talking about
applications here.
> For example set f.line_buffering = False for performance and break your logging. Creating a new TextIOWrapper for own needs looks safer.
Now you may have two TextIOWrappers alive wrapping the same buffered IO
object.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30526>
_______________________________________
More information about the Python-bugs-list
mailing list