GNU bug report logs - #23095
24.5; python-shell-unbuffered causes problems on Windows

Previous Next

Package: emacs;

Reported by: Will Wykeham <will <at> wykeham.net>

Date: Tue, 22 Mar 2016 22:18:02 UTC

Severity: normal

Tags: fixed, patch

Merged with 21376

Found in versions 24.5, 25.0.50

Fixed in version 26.1

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log

Message #16 received at control <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Will Wykeham <will <at> wykeham.net>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 23095 <at> debbugs.gnu.org
Subject: Re: bug#23095: 24.5;
 python-shell-unbuffered causes problems on Windows
Date: Sun, 03 Dec 2017 00:43:38 -0500

close 23095 26.1
unarchive 21376
merge 23095 21376
quit

Will Wykeham <will <at> wykeham.net> writes:

>>> I haven't got to the bottom of why unbuffered is causing this
>>> problem. My suspicion is that it relates to the fact that
>>> PYTHONUNBUFFERED on Windows also causes python to process stdin/stdout
>>> as binary (which also affects line ending processing).
>>
>> On Windows, Emacs communicates with subprocesses via pipes, which are
>> buffered.
>
> Ah. In which case, it sounds like the appropriate thing would be to
> set the default value of 'python-shell-unbuffered' to nil on Windows.

So it turns out this is actually some weird bug in w32 Python 2.x, we
work around it in Emacs 26 now.

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21376#11
This bug report was last modified 7 years and 174 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.