4 ms·
The error is "IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection" I always
by aitoehigie 18y ago
The error is "IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection"
I always ensure that the Python interpreter is part of my firewalls exceptions so it is never blocked.
- lilspikey 18y agoAh, so that sounds more like a problem with IDLE than with Python itself. You shouldn't have any issues running Python interpretors normally.
- Erwin 18y agoIt's an IDLE IDE problem as lilspikey mentioned rather than Python itself. From what I can tell, IDLE listens on a fixed port on localhost in order to communicate with the actual Python interpreter, so starting multiple IDLEs may not work. If you run multiple instances of just "python" from the shell (assuming UNIX), there is no problem. GIL is not involved here, it only comes into play when you have multiple threads in a single process. I don't use IDLE, but http://mail.python.org/pipermail/patches/2006-July/020329.html http://mail.python.org/pipermail/patches/2006-July/020329.ht... suggests there's some "-n" switch you can IDLE with that alleviates the problem somehow.
- schtog 18y agoI get this too sometimes but have never been able to figure out the problem. It can happen after I have started and closed the interpeter and then start it again.