Either IDLE Can't Start a subprocess or a firewall software firewall is blocking the connection (Win)--Battlin McAfee

[W. eWatson]

Alf P. Steinbach wrote:
> * W. eWatson:
>> See Subject msg from Python 2.5 Win XP. It is preceded by a "Socket 
>> Error". It happened while I had a simple program displayed, and I 
>> wanted to see the shell. The msg occurred when I pressed Shell on Run 
>> from the menu. I played around for awhile, but got nowhere. Same msg. 
>> I did remove my McAfee firewall protection, and it worked once, but 
>> reverted to not working.
>>
>> I rebooted and the first time I could use Shell, it succeeded. After 
>> that it failed. Comments? Geeze! Mcaffe turned on the firewall again 
>> after the reboot.
>>
>> All seems well now. Nope. McAfee turned the firewall back on. It 
>> decided to warn me it was off, but now has allowed me to ignore the 
>> fact it is "no longer protecting me". I'll just let Win firewall do 
>> that, thank you.
>>
>> Nope it's back. I'll just stop here and let anyone who wants to just 
>> chime in. If I get it to stop, I'll be back.
> 
> I recall vaguely some similar problem caused by a program attempting to 
> connect to localhost, and the solution then was to edit the hosts file 
> (don't ask me for details, but perhaps that'll help you search: that 
> problem had entirely to do with Windows' very over-zealous "security" 
> measures).
> 
> 
> Cheers & hth.,
> 
> - Alf
As it turns out, I can "sneak" around it, so I'm putting it aside.