Issue 32730: Allow py launcher to launch other registered Pythons

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/76911

classification

Title:	Allow py launcher to launch other registered Pythons
Type:	enhancement	Stage:
Components:	Windows	Versions:	Python 3.8, Python 3.7, Python 3.6, Python 2.7

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	paul.moore, petsuter@gmail.com, steve.dower, tim.golden, uranusjr, zach.ware
Priority:	normal	Keywords:

Created on 2018-01-31 15:57 by petsuter@gmail.com, last changed 2022-04-11 14:58 by admin.

Messages (3)
msg311338 - (view)	Author: Peter Suter (petsuter@gmail.com)	Date: 2018-01-31 15:57
For example Anaconda Python is registered under HKEY_LOCAL_MACHINE\Software\Python\ContinuumAnalytics\Anaconda36-64\ as described in PEP 514 "Python registration in the Windows registry" . The py launcher from PEP 397 however ignores that and only considers HKEY_LOCAL_MACHINE\Software\Python\PythonCore\ registrations. There seems to be no mechanism to register Anaconda Python with the py launcher. Anaconda considers this a bug in the Python launcher. https://github.com/ContinuumIO/anaconda-issues/issues/149#issuecomment-361922640 Shouldn't this be possible? Maybe via py.ini [defaults]?
msg311378 - (view)	Author: Steve Dower (steve.dower) *	Date: 2018-01-31 21:39
Yep, this was part of the plan. Just hasn't happened yet (it probably requires a significant rewrite of the launcher which nobody has volunteered to do or found the time for). I thought I had another open bug on this too... if someone finds it, feel free to dup this one.
msg313188 - (view)	Author: Steve Dower (steve.dower) *	Date: 2018-03-03 17:53
Since I took the time to do a brain dump of my thinking here, feel free to review/contribute to https://github.com/zooba/PyLauncher/wiki Note that the code in that repo doesn't match the wiki page, and while I think it's good code I do now think it's the wrong approach. So ignore that and just read the "spec"