Emacs interactive Python mode delays evaluation

Asked Feb 16 '14 at 10:22

Active Feb 16 '14 at 10:22

Viewed 86 times

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

How do I fix this?

asked Feb 16 '14 at 10:22

marczellm

1,224
2
18
42

Maybe it wants you to confirm if you wish to evaluate `nonsense`? – devnull Feb 16 '14 at 10:23
@devnull then how should I "change my mind"? – marczellm Feb 16 '14 at 10:25
Since you were the one to start, it probably doesn't let you have a choice regarding that :) – devnull Feb 16 '14 at 10:27
Odd. What do you get if you set `nonsense = 1` and then try to evaluate `nonsense`? – user2357112 Feb 16 '14 at 10:47
@user2357112 I type `nonsense`, press Enter, no output; type `nonsense=1`, press Enter, get the error message related to the first prompt; then type `nonsense` and press Enter and get 1. – marczellm Feb 16 '14 at 11:02
I'm unable to duplicate this with 3.3.4, Emacs 24.3, and Ubuntu or Fedora. Odd. – daniel gratzer Feb 16 '14 at 14:45
@jozefg Then quite possibly it's a Windows-only problem. – marczellm Feb 16 '14 at 14:58
@marczellm, do you get similar behaviour running `python` directly from `cmd.exe`? – ChrisGPT was on strike Feb 16 '14 at 15:37

Emacs interactive Python mode delays evaluation

0 Answers0