New submission from clikkeb :
It's a common issue that IDLE cannot start on Windows because
"IDLE's subprocess didn't make connection.Either IDLE can't start a subprocess
or personal firewall software is blocking the connection."
Everyone claim that the user
clikkeb added the comment:
Thanks for your answer.
Trying to understand how IDLE uses HOMEPATH and USERPROFILE Windows
variables, I have found the following information:
1) it seems that when executed via Windows command prompt (cmd.exe),
os.path.expanduser refers to USERPROFILE to
clikkeb added the comment:
I think that lines 207-210 of GetUserCfgDir should be modified like this:
try:
sys.stderr.write(warn)
except (IOError, AttributeError):# <
pass#^^
because when you start IDLE via pythonw.exe (that sets sys.stderr to "Non
clikkeb added the comment:
It is one of the possible solutions.
In combination with the "writable flag" solution, you might create a class
variable in IdleConf (e.g. "user_cfg") that contains the user's home directory;
such variable will be initialized to an empty st
