[issue6628] IDLE freezes after encountering a syntax error

2011-01-29 Thread Ned Deily
Ned Deily n...@acm.org added the comment: For the record: The problem was caused by a minor change in IDLE during the port of IDLE from 2.x to 3.x. It is fixed by the changes for Issue11053: r88234 (3.2rc2) and r88242 (planned for 3.1.4). -- assignee: ronaldoussoren - ned.deily

[issue6628] IDLE freezes after encountering a syntax error

2010-11-27 Thread Ned Deily
Ned Deily n...@acm.org added the comment: This issue was reported again in Issue9763; at the time, I overlooked your original report. As there is a more recent discussion of it over there, I am going to close this as a duplicate and add you to the nosy list there. -- resolution: -

[issue6628] IDLE freezes after encountering a syntax error

2009-08-04 Thread Ned Deily
Ned Deily n...@acm.org added the comment: I can't reproduce a hang with the python.org 3.1 IDLE on either 10.4 or 10.5 and with the system Tcl/Tk or with a newer Active Tcl/Tk 8.4 installed. Do you have another version of Tcl/Tk installed in /Library/Frameworks? Can you give a step-by-step

[issue6628] IDLE freezes after encountering a syntax error

2009-08-04 Thread brian
brian omniscient.br...@gmail.com added the comment: I have Tcl/tk 8.4.7 installed. To reproduce the hang on my machine: open IDLE new window enter the following code: for i in range(10) print(i) run module (saved as test.py) interpreter complains (shell is still responsive at this

[issue6628] IDLE freezes after encountering a syntax error

2009-08-04 Thread Ned Deily
Ned Deily n...@acm.org added the comment: Thanks, I'm now able to reproduce on both 10.4 and 10.5 with the Apple- supplied Tcl/Tk 8.4.7 but apparently not with a newer Tcl/Tk nor with 2.6.2. Investigating further. -- ___ Python tracker

[issue6628] IDLE freezes after encountering a syntax error

2009-08-02 Thread brian
New submission from brian omniscient.br...@gmail.com: Running Python 3.1/ IDLE, which was installed on top of a Python 2.5.4 install, Mac OSX 10.4 This seems like such an obvious bug, but I can't find it in the current list of issues - so I suspect that it may not be reproducible on other