This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Maja Tomic, eryksun, kbk, paul.moore, roger.serwy, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2015-10-24.03:35:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I see the problem: there is only one IDLE icon for all users, so you need the env var to customize for each user, which you cannot use. Staying with the python install directory, as before, should be better.  We never got any complaints about that.  But the new install locations are more problematical.

I have also thought of adding an new startup option, but it should only apply if IDLE is started with the ICON.  When started at the command line, it should start at the current directory of the console, as it does now, so '.' refers to that directory.  Ironically, a current directory of .../system32 would be a good indicator.  I need to see what is in sys.argv after the different start methods.

This issue is currently only for Windows. I don't know what happens on other systems or whether they could stand improvement.
Date User Action Args
2015-10-24 03:35:45terry.reedysetrecipients: + terry.reedy, kbk, paul.moore, tim.golden, roger.serwy, zach.ware, eryksun, steve.dower, Maja Tomic
2015-10-24 03:35:44terry.reedysetmessageid: <>
2015-10-24 03:35:44terry.reedylinkissue25450 messages
2015-10-24 03:35:43terry.reedycreate