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:

1: Socket Error: Connection refused
2: IDLE's subprocess didn't make connection. Either IDLE can't start a 
subprocess or personal firewall is blocking the connection.

The code written in IDLE that triggers the problem can be something 
simple like:
>>> a = 'hello world'
>>> print a

I have to reboot to get past the error.
I'm only getting the error when running vista and xp theres no problom 
in any of the other systems i'v tried (mainly linux)
I should mention that the error dosn't come every time I "kill" IDLE, I 
would say about every 3rd run, or there about.
I'v tried removeing/killing windows owen firewall and then running IDLE 
but with the same result.
Like I said, i been look around fore a "fix" fore this but havent found 
any...
If I have made a "double post" please let me know and remove this 
post....

1. Which version of Python / IDLE are you running?
2. Why do you "have to kill" IDLE instead of doing a normal quit?

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.

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.

3.0 is closed to fixed and 2.6 is security fix only.
This is otherwise a duplicate of similar issues.