[issue1613500] Write mode option for fileinput module.

Change by Berker Peksag : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 -Python 3.5 ___ Python tracker ___

[issue1613500] Write mode option for fileinput module.

Berker Peksag added the comment: New changeset be6dbfb43b89989ccc83fbc4c5234f50f44c47ad by Berker Peksag in branch 'master': bpo-1613500: Don't hardcode output file mode in fileinput.FileInput (GH-12986) https://github.com/python/cpython/commit/be6dbfb43b89989ccc83fbc4c5234f50f44c47ad

[issue1613500] Write mode option for fileinput module.

Change by Berker Peksag : -- pull_requests: +12909 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1613500] Write mode option for fileinput module.

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1613500 ___ ___

[issue1613500] Write mode option for fileinput module.

R. David Murray added the comment: As far as I can see from a quick look, the problem this patch addresses still exists in Python3, and in Python3 it be (more of?) a bug. That is, the output file is opened in text mode, regardless of whether the input mode was text or bytes. I'm not sure

[issue1613500] Write mode option for fileinput module.

Mark Lawrence breamore...@yahoo.co.uk added the comment: This looks like a sizeable patch but the bulk of the changes are to test_fileinput.py. Assigning to myself to take forward, I've got to start sometime. Before I really start moving are there any basic objections to either the original

[issue1613500] Write mode option for fileinput module.

Changes by Daniel Diniz aja...@gmail.com: -- stage: - patch review type: - feature request versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1613500 ___