IDLE problem

Problems? Post here...
Post Reply
User avatar
moudy
Technology Enthusiast
Technology Enthusiast
Posts: 688
Joined: 10 Feb 2009, 17:00
15
Location: Beirut, Lebanon

IDLE problem

Post by moudy »

Hello every one, lone time :)
I have this problem that I'm newly facing.
I used to open IDLE and no problems occurred.
Suddenly I started to get this error:

Code: Select all

IDLE Subprocess Error
Socket Error: No connection could be made because the target machine actively refused it
followed by this error:

Code: Select all

Subprocess Startup Error
IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection.
Also if I open a .py file via right click ---> open with IDLE, it opens normally.
I would just like to know if this could be solved ?
Thanks for any help.
mahmoud_shihab@hotmail.com

User avatar
bad_brain
Site Owner
Site Owner
Posts: 11636
Joined: 06 Apr 2005, 16:00
19
Location: In your eye floaters.
Contact:

Re: IDLE problem

Post by bad_brain »

hmm...have you checked the processes? could be that an old process wasn't finished properly and is still using the socket... :-k
Image

User avatar
moudy
Technology Enthusiast
Technology Enthusiast
Posts: 688
Joined: 10 Feb 2009, 17:00
15
Location: Beirut, Lebanon

[solved] Re: IDLE problem

Post by moudy »

Job well done bad brain :) thanks for the advice.
I really didn't even bother to look at process explorer. I figured out that there were two process under the name python.exe running, and its obvious that python isn't running on my desktop.
Few days ago I was working with urllib2 module, probably some thing went wrong while connecting to a website, most probably this was the problem.
I should keep and eye on process explorer more often :D
mahmoud_shihab@hotmail.com

User avatar
bad_brain
Site Owner
Site Owner
Posts: 11636
Joined: 06 Apr 2005, 16:00
19
Location: In your eye floaters.
Contact:

Re: IDLE problem

Post by bad_brain »

good you found the reason... :D
I had similar problems already with apache for example, luckily the error message are more helpful there because you get a "socket already in use" notice. if a socket can't be used the reason in most cases (imo) is that is IS already used....so it was the best guess.... :wink:

and yeah, process explorer and also tcpview are the most valuable tools for general troubleshooting on Windows systems... :D
Image

Post Reply