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 pitrou
Recipients amaury.forgeotdarc, brian.curtin, gvanrossum, pitrou, v+python
Date 2011-01-06.10:36:22
SpamBayes Score 2.1883901e-05
Marked as misclassified No
Message-id <1294310179.3716.64.camel@localhost.localdomain>
In-reply-to <1294307045.25.0.679082146508.issue10841@psf.upfronthosting.co.za>
Content
> So -u does do 2/3 of what my windows_binary() does :)  Should I switch
> my test case to use stderr to demonstrate that it doesn't help with
> that?

Well, judging by the history of this code, selectively putting -u in
binary mode may be justified by the fact that Python 2 relied on the C
runtime's stdio FILE pointers, and therefore on the C runtime's own
newline translation. I would say that Python 3 should put all stdio fds
in binary mode, regardless of the -u switch.
History
Date User Action Args
2011-01-06 10:36:24pitrousetrecipients: + pitrou, gvanrossum, amaury.forgeotdarc, v+python, brian.curtin
2011-01-06 10:36:22pitroulinkissue10841 messages
2011-01-06 10:36:22pitroucreate