Python error - IDLE subprocess did not establish a connection. Either IDLE cannot start, or personal firewall software blocks the connection

Question

I am new to programming and I decided to learn Python first, so

I installed Python, the latest version 3.4. and I'm trying to open Python IDLE (GUI) mode, so when I open, I get the message: "The IDLE subprocess was not connected. Either IDLE cannot start or the personal firewall software blocks the connection."

My firewall is not a problem. I put Python on it. I also tried reinstalling it and it did not diffirence. So please, if somenone can help!

Thank you for your time: D

Answer 1

Delete all newly created .py files in the directory with Python. like random.py, end.py - this was my problem that caused the same notification window. The cause of file name conflicts.

Answer 2

This may be a common problem that occurs when you have a file with the same name in one of Python in the current directory (links: Unable to start Python via IDLE from Explorer [2013] - the IDLE subprocess did not establish a connection )

This also seems to happen if you have the wrong environment variables like HOMEPATH USERPROFILE (links: Issue 14576: IDLE: inconsistent use of HOMEDRIVE, HOMEPATH and USERPROFILE on Windows )

I found another related question: Python IDLE subprocess error?

My advice if there is no answer there: Google can be your friend! 3 tips come out of this :-)

Answer 3

Simple ... rename your .py file with some name different from any keyword name such as "random.py" that already exists in the python package.

Eg. I named one file "random.py". An error has occurred. I renamed it to "random_demo.py". It worked. Different naming eliminates the ambiguity problem between an existing file and a newly created file with the same name.

Answer 4

I fixed it, I needed to run IDLE with administrator privileges. (I am using Windows 7 x64). Hope this helps.

Answer 5

The fix is here .

Open task manager, run pythonw.exe if you find 2 or more instances. Should work after that.

Answer 6

For me: the drive referenced by HOMEDRIVE is not writable. I checked this by running simple mode explicitly using python.exe, not pythonw.exe:

 C:\coding\xyz>"C:\Python27\Lib\idlelib\..\..\python.exe" "C:\Python27\Lib\idlelib\idle.pyw" Warning: unable to create user config directory P:\.idlerc Check path and permissions. Exiting! 

Answer 7

I had a similar problem with a file called "test.py" and Python 2.7.9 - renaming the file to something else that solved my problem. After checking, I noticed that there is a file with the same name in the Python27 \ Lib folder.

This seems to be a bug in IDLE.

Answer 8

Just the same problem. So he was removed and reinstalled, and he earned 10 minutes. The key with Windows computers is to delete the old directory (C: \ Python27 \, because windows really delete things), and when reinstalling, specify the new directory (C: \ Python279 \ or whatever you choose to call it).

I am using Win 10 with Python 2.7.9.

Answer 9

Go to C: / Users / [your user] / AppData / Local / Programs / Python / Python35-32 and delete or rename each * .py file in this directory, which is named after a specific method, function, module or library. Then run IDLE. Must work.

I hope I can help

Answer 10

My problem was that the .py file was not on my local machine. It was in a shared directory.

After moving the file to the local computer, I stopped receiving the error message.

Answer 11

Just to mark my specific problem, this happens to me when my RAM is full and my processor is loading.

The problem is a network socket timeout on IPC links between the RPC subprocess.
This is a poor design (unsafe and malfunctioning) that is commonly used for IPC instead of technology channels.

The fix is ​​to clear some memory and processor usage and wait a minute before trying again.
And for developers, the fix is ​​to stop using sockets for IPC and use the proper process channels.

Yes, this is the same socket timeout problem that you encountered in your browser, although in modern browsers the page just stops loading instead of displaying a timeout error screen.
(note that this implies a case of a good WAN connection with a local timeout)