New submission from Márton Marczell:
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
Python 2 does not do this. I've filed an Emacs bug report
(http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17304) and got the response to
try this on the command line (where cat.exe is from an MSYS installation):
python 2>&1 | cat.exe
and it behaves the same way as in Emacs.
----------
components: Windows
messages: 217861
nosy: marczellm
priority: normal
severity: normal
status: open
title: Python 3 pipe handling breaks python mode in emacs on Windows
type: behavior
versions: Python 3.3
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue21425>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
