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 BreamoreBoy, Jimbofbx, ncoghlan, r.david.murray, roger.serwy, terry.reedy
Date 2014-06-08.23:40:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There already is an idlelib/idle.bat that starts the corresponding python with

set CURRDIR=%~dp0
start "IDLE" "%CURRDIR%..\..\pythonw.exe" "%CURRDIR%idle.pyw" %1 %2 %3 %4 %5 %6 %7 %8 %9

Arguments added to the .bat command are passed on. So the enhancement requested already exists.

C:\Programs>python34\lib\idlelib\idle.bat, for instance, starts 3.4, and changing '34' to '33' or '27' starts 3.3 or 2.7.

python -E ignores PYTHON* environment variables. Unfortunately, this seems to prevent python from running idle. Adding -E to the above or directly to
C:\Programs\Python34>pythonw.exe Lib/idlelib/idle.pyw -E
results in a new prompts with no visible action. Since I do not have any PYTHON* vars to ignore, this puzzle me. Does this indicate a bug in the startup handling of -E? (Nick?)

Except for this puzzle, I would close this as a third party issue.
Date User Action Args
2014-06-08 23:40:43terry.reedysetrecipients: + terry.reedy, ncoghlan, roger.serwy, r.david.murray, BreamoreBoy, Jimbofbx
2014-06-08 23:40:43terry.reedysetmessageid: <>
2014-06-08 23:40:43terry.reedylinkissue15780 messages
2014-06-08 23:40:43terry.reedycreate