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 srid
Recipients srid
Date 2009-06-29.20:45:19
SpamBayes Score 1.6531221e-13
Marked as misclassified No
Message-id <1246308322.32.0.750084238969.issue6378@psf.upfronthosting.co.za>
In-reply-to
Content
On Mon, 29 Jun 2009 09:56:53 -0700, Trent Mick <trentm@activestate.com>
wrote:

> Sridhar Ratnakumar wrote:
>> I installed ActivePython-3.1 to C:\Python31 but disabled the 
installer
>> option "Register as default Python" .. because, I use Python-2.6 by  
>> default.
>>
>> However, this disabling broke 3.1's IDLE. Clicking on 'idle.bat' or
>> 'idle.py' or 'idle.pyw' in C:\Python31\Lib\idle\ directory opens 
Python
>> 2.6's IDLE.
>>
>> Since the installer knows the path to Python - C:
\Python31\python.exe -
>> does it make sense to patch the idle.bat file to use this binary?
>
> IIRC there is a special NT batch file syntax that you can use do that
> idle.bat will look for python.exe in a relative path, so that you 
won't
> have to patch idle.bat after install (which would be a pain).
>
> Here, use this for idle.bat:
>
>    @echo off
>    set CURRDIR=%~dp0
>    start %CURRDIR%..\..\pythonw.exe idle.pyw
>
> Perhaps you could add a bug to core Python to change idle.bat to be 
that?
>
>
> Trent
>
History
Date User Action Args
2009-06-29 20:45:22sridsetrecipients: + srid
2009-06-29 20:45:22sridsetmessageid: <1246308322.32.0.750084238969.issue6378@psf.upfronthosting.co.za>
2009-06-29 20:45:20sridlinkissue6378 messages
2009-06-29 20:45:20sridcreate