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 string by IdleConf.__init__.
O
Andrew Svetlov added the comment:
I guess IdleConf should to have flag like 'writable'.
If user environment points to invalid location (or there are no write access)
this flag should be set.
It flag can affect IDLE configuration dialog: user should be notified what him
changes will not be perm
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 "None"),
the f
R. David Murray added the comment:
It certainly is worthwhile pursing this in some fashion, since at the very
least the existing error message needs to be improved. But perhaps there is
something more that can be done to gracefully handle this case, instead. I
think the next interesting que
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 determine
Roger Serwy added the comment:
I can confirm that setting HOMEPATH to a non-existent directory will prevent
IDLE from starting when using idle.bat. If you modify idle.bat such that
python.exe is called instead of pythonw.exe, then IDLE starts normally, but
with this console message:
Warnin
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 should set the firewal so that IDLE
