Message125595
| Author |
gvanrossum |
| Recipients |
amaury.forgeotdarc, benjamin.peterson, brian.curtin, gvanrossum, pitrou, v+python, vstinner |
| Date |
2011年01月06日.22:20:43 |
| SpamBayes Score |
2.715035e-09 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTikMwJq3GxZFHcAnsyPcowe-AwPbiADYgSG+ajNv@mail.gmail.com> |
| In-reply-to |
<1294348849.03.0.39524990341.issue10841@psf.upfronthosting.co.za> |
| Content |
On Thu, Jan 6, 2011 at 1:20 PM, STINNER Victor <report@bugs.python.org> wrote:
> I don't know the effect of _setmode(stderr, O_BINARY) on calls to fputs(stderr, ...) in Py_FatalError().
On Windows it will write lines ending in LF only instead of CRLF. Most
tools to read text files should be able deal with that by now,
conditioned as they are by many years of Unix developers doing Windows
stuff on the side. (Somebody should test what Notepad does though. :-)
I don't know any other supported platforms where O_BINARY exists and
is not a no-op (but I haven't really looked :-). |
|