Idle problem

[Brent W. Hughes]

Sometimes when I try to start up idle.py (by double-clicking on the icon), I
get the message:
Python subprocess socket error: Connection refused, retrying....
It repeats the message a couple of times and then prints:
Connection to Idle failed, exiting.

Any idea what's going on?

 

[Ian J Cottee]

Sometimes when I try to start up idle.py (by double-clicking on the icon), I
get the message:
Python subprocess socket error: Connection refused, retrying....
It repeats the message a couple of times and then prints:
Connection to Idle failed, exiting.

Any idea what's going on?

http://aspn.activestate.com/ASPN/Mail/Message/python-dev/1748187

Doesn't offer any conclusions but might point you in the right direction.

Ian

 

[Ben McGinnes]

Brent W. Hughes([email protected])@Thu, Aug 26, 2004 at 12:37:23AM +0000:

Sometimes when I try to start up idle.py (by double-clicking on the icon), I
get the message:
Python subprocess socket error: Connection refused, retrying....
It repeats the message a couple of times and then prints:
Connection to Idle failed, exiting.

I just fired up Idle and it displayed the following message:

****************************************************************
Personal firewall software may warn about the connection IDLE
makes to its subprocess using this computer's internal loopback
interface. This connection is not visible on any external
interface and no data is sent to or received from the Internet.
****************************************************************

Which means you could be running some firewall software locally which
is not allowing Idle to open the sockets it requires. You should
change this to allow all connections on the loopback.


Regards,
Ben

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQS2EeDcaxb+gSuMTEQJ9SQCeLB1xUnQtsaL29LxnCfW9J8FSP14Amwff
SqFntS6WjYn1uo3DJrUF1jq2
=I9KT
-----END PGP SIGNATURE-----

 

[Sibylle Koczian]

http://aspn.activestate.com/ASPN/Mail/Message/python-dev/1748187

Doesn't offer any conclusions but might point you in the right direction.

Seems to suggest two possibilities: the firewall issue mentioned in Ben
McGinnes' answer or else no sockets - if a machine is not part of any
local network and has no network software at all installed. If I
understand that thread correctly that might even be the case if it's
connected to the internet by modem and dial-up access. I'd think a "ping
localhost" should show this.

Koczian

--
Dr. Sibylle Koczian
Universitaetsbibliothek, Abt. Naturwiss.
D-86135 Augsburg

Tel.: (0821) 598-2400, Fax : (0821) 598-2410
e-mail : (e-mail address removed)-Augsburg.DE