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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, asvetlov, bebac, jmfauth, mhammond, tarek, techtonik, terry.reedy
Date 2009-04-01.15:10:21
SpamBayes Score 7.5290984e-05
Marked as misclassified No
Message-id <1238598623.19.0.0955112626129.issue4015@psf.upfronthosting.co.za>
In-reply-to
Content
I agree.
In any case, double-clicking on a .py file should start an "installed"
interpreter, that is one listed in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\X.Y\InstallPath

Today starting a .py file only open the last installed Python interpreter.
With this proposal, the launcher choose the "best" installed interpreter
for the given script, and falls back to the last installed one.

There may be different definitions of "best". The algorithm could look
like this:
- if the first line is
    #! c:/some/path/to/python.exe
  and the registry contains an installation with 
    InstallPath="c:/some/path/to"
  choose this one.
- if the first line matches
    #! c:/python/([1-9])([0-9])/python.exe
  and if the following registry key exists:
    HKEY_LOCAL_MACHINE/SOFTWARE/Python/PythonCore/\1.\2/InstallPath
  choose this one.
- else, use the last installed interpreter.
History
Date User Action Args
2009-04-01 15:10:23amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, mhammond, terry.reedy, techtonik, tarek, jmfauth, bebac, asvetlov
2009-04-01 15:10:23amaury.forgeotdarcsetmessageid: <1238598623.19.0.0955112626129.issue4015@psf.upfronthosting.co.za>
2009-04-01 15:10:22amaury.forgeotdarclinkissue4015 messages
2009-04-01 15:10:21amaury.forgeotdarccreate