GNU bug report logs - #17304
Python mode delays evaluation

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: dalokmarcinak <at> gmail.com, 17304 <at> debbugs.gnu.org
Subject: Re: bug#17304: Python mode delays evaluation
Date: Sat, 03 May 2014 09:20:38 +0300

> From: Glenn Morris <rgm <at> gnu.org>
> Date: Fri, 02 May 2014 21:16:35 -0400
> Cc: 17304 <at> debbugs.gnu.org
> 
> Márton Marczell wrote:
> 
> > When I run a Python 3.3.4 prompt inside Emacs 24.3 on Windows 7, correct
> > commands are evaluated immediately, but incorrect ones are delayed (I have
> > to press Enter one more time), as seen below:
> >
> >     >>> 1
> >     1
> >     >>> nonsense
> >     >>>
> >     Traceback (most recent call last):
> >     File "<stdin>", line 1, in <module>
> >     NameError: name 'nonsense' is not defined
> [...]
> > In GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601)
> 
> FWIW, I cannot reproduce this with Emacs 24.3 and Python 3.4.0 on GNU/Linux.

Probably because of buffering differences: pipes are fully buffered on
Windows, even those used for stderr.  If that is indeed the case, I
don't think this problem can be fixed in Emacs.

To the OP: do you have the same problem if you redirect Python's
output streams in the shell, using "2>&1 |" ?  The other side of the
pipe could be cat.exe, for example.

Previous Next

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