Python error - IDLE's subprocess didn't ma

Question

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

I installed Python, latest version 3.4. and I am trying to open Python IDLE(GUI) mode, so when I open I get message "IDLE's subprocess didn't make connection. Either IDLE can't start or personal firewall software is blocking connection.".

My firewall is not problem beacuse I put Python throught it. I also tried to reinstall it and it didnt made diffirence. So please if somenone can help!

Thank you on your time :D

Answer 1

It may be a common problem that happens when you have in you current directory a file with same name on one from Python (references : Can't run Python via IDLE from Explorer [2013] - IDLE's subprocess didn't make connection)

It seems it can also happen if you have incorrect environment variables such as HOMEPATH USERPROFILE (references : Issue 14576: IDLE: inconsistent use of HOMEDRIVE, HOMEPATH, and USERPROFILE on Windows)

I've found another related question : Python IDLE subprocess error?

My advice if the answer is not there : google may be your friend ! The 3 clues above come from there :-)

Answer 2

Delete all newely created .py files in the directory with Python. for example random.py, end.py - that was my problem that caused the same notification window

Answer 3

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

Seems to be a bug in IDLE.

Answer 4

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

Answer 5

For me: The drive pointed to by HOMEDRIVE was not writeable. I checked this by running idle the hard way, explicitly using python.exe rather than 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 6

The fix is here .

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