Mark Lawrence added the comment:
@Terry what is your take on this?
--
nosy: +BreamoreBoy, terry.reedy
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15862
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15862
___
___
Cemal Duman added the comment:
Hi,
yes exactly...
I changed my home by using below commands.
C:\Python27set HOME=C:\
C:\Python27python -m idlelib.idle
it is working. But if i reboot my computer HOME changes again to network drive.
I think sth abour corporate programs rewrites this paramters.
Roger Serwy added the comment:
In your original message, did IDLE eventually start when you ran:
C:\Python27python.exe Lib\idlelib\idle.py
? If yes, then the bug is likely due to issue13582.
If I understand correctly, when you reboot your computer, IDLE won't launch
from the shortcut in
Roger Serwy added the comment:
With Python 2.7.3 on Win7, I tried the following:
C:\Python27set HOME=H:\
C:\Python27python -m idlelib.idle
I do receive the same warning messages described by Cemal, since I don't have a
valid H:\ drive. However, IDLE is responsive. Running IDLE using
New submission from Cemal Duman:
Hi
Unfortunately i'm using Vista on my corparate laptop I can open my Python CLI
without any problem but IDLE is not responding. When i started idle.py by
issuing following command:
C:\Python27python.exe Lib\idlelib\idle.py
I see following output:
Roger Serwy added the comment:
IDLE not responding is likely due to Issue13582, since the warning message
would cause IDLE to terminate abruptly when launched with pythonw.exe.
What does os.path.expanduser(~) evaluate to when executed from the IDLE shell?
--
nosy: +serwy
