[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Nick Coghlan added the comment: Aye, let's close this for now - swapping streams out has enough other problems with stale references to the original stream that using reconfigure() to update the existing stream in place is usually going to be the better option. -- resolution: ->

[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Inada Naoki added the comment: TextIOWrapper now has reconfigure() method. Can this issue be closed? -- nosy: +inada.naoki ___ Python tracker ___

[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Mark Lawrence added the comment: @Nick would you like or even need this in 3.5? -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14017

[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +pitrou stage: - needs patch type: - enhancement versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14017

[issue14017] Make it easy to create a new TextIOWrapper based on an existing

Nick Coghlan ncogh...@gmail.com added the comment: Updating issue title, since I realised this doesn't work in 3.2 either (the newline argument also isn't available for introspection - newlines is not the same thing) Possible API signature: _missing = object() def rewrap(self,