Terry J. Reedy tjre...@udel.edu 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
Christopher Altona calto...@gmail.com 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
Changes by Daniel Diniz aja...@gmail.com:
--
nosy: +gpolo
priority: - normal
stage: - test needed
type: crash - behavior
versions: +Python 2.6, Python 3.0 -Python 2.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2708
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.
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]
http://bugs.python.org/issue2708
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 popping up:
