clikkeb clik...@gmail.com 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
clikkeb clik...@gmail.com 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
clikkeb clik...@gmail.com 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
New submission from clikkeb clik...@gmail.com:
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
.
--
So, if you don't want IDLE to raise a connection error, make sure that
HOME, USERPROFILE or the combination of HOMEPATH and HOMEDRIVE
represent an existent and writable directory.
Best regards.
clikkeb
--
http://mail.python.org/mailman/listinfo/python
.
--
So, if you don't want IDLE to raise a connection error, make sure that
HOME, USERPROFILE or the combination of HOMEPATH and HOMEDRIVE
represent an existent and writable directory.
Best regards.
clikkeb
--
http://mail.python.org/mailman/listinfo
