[issue2708] IDLE subprocess error

Terry J. Reedy added the comment: 3.0 is closed to fixed and 2.6 is security fix only. This is otherwise a duplicate of similar issues. -- nosy: +terry.reedy resolution: -> out of date status: open -> closed ___ Python tracker

[issue2708] IDLE subprocess error

Christopher Altona added the comment: I found that if I go into the Windows Task Manager and end (somtimes both of) the Python processes, the program will run properly the next time I open it. Hope this helps. -- nosy: +ChrisAltona ___ Python track

[issue2708] IDLE subprocess error

Changes by Daniel Diniz : -- nosy: +gpolo priority: -> normal stage: -> test needed type: crash -> behavior versions: +Python 2.6, Python 3.0 -Python 2.5 ___ Python tracker ___

[issue2708] IDLE subprocess error

Kristian Lauridsen <[EMAIL PROTECTED]> added the comment: Python 2.5.2 IDLE 1.2.2 It dosnt matter how i try to "end" IDLE: red cross, close(alt+F4), exit (Ctrl+Q) or writing exit(), it will ask me to kill the program. I dont think it's IDLE im "killing" but the program im writing. _

[issue2708] IDLE subprocess error

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: 1. Which version of Python / IDLE are you running? 2. Why do you "have to kill" IDLE instead of doing a normal quit? -- nosy: +kbk __ Tracker <[EMAIL PROTECTED]>

[issue2708] IDLE subprocess error

New submission from Kristian Lauridsen <[EMAIL PROTECTED]>: Hi all. I'w been looking for an answer to this. If I use IDLE for som "just fore fun" programming and then exit, I have to "kill" IDLE, dispite theres nothin "running" persay, then when i start IDLE again I get too error messages popp