Zachary Ware added the comment:
Terry: Is python.bat sufficient for your uses? It's created by
PCbuild/python.vcxproj, and always points to whatever interpreter you built
last.
If it's not enough, maybe it could be extended to invoke any already-built
interpreter?
--
__
Terry J. Reedy added the comment:
I presume there is already a dead registry entry problem if someone simply
deletes the pythonxy directory. (I know, very bad idea.) On the other hand,
deleting a git repository directory *is* the thing to do. While listing
entries and paths, py could check
Paul Moore added the comment:
Hmm, thinking a bit further, are you just suggesting registering the build as
-3.7? What if I were to build the 3.6 branch? Would that overwrite my "real"
3.6 registry entries?
As things stand, the launcher can only register two copies of Python for any
given min
Paul Moore added the comment:
I'd be wary of leaving out of date registry entries around. Maybe make it a
separate script (or part of build.bat but requiring a command line flag to
request it)?
Alternatively (or as well) we could have a cleanup command that removes
registry entries for workin
New submission from Terry J. Reedy:
While working on patches for python, typing
path\repository\PCbuild\win32\python-d.exe is an error-prone pain. I would
really like to be able to run locally built binaries with py.Could
pcbuild/build.bat register binaries that it successfully builds? A
