[issue27602] Enable py launcher to launch repository Python.

2021-03-20 Thread Gregory P. Smith
Change by Gregory P. Smith : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27602] Enable py launcher to launch repository Python.

2021-03-20 Thread Eryk Sun
Eryk Sun added the comment: See also bpo-30405, which has more discussion about supporting PEP 514 in the launcher. -- ___ Python tracker ___

[issue27602] Enable py launcher to launch repository Python.

2021-03-17 Thread Eryk Sun
Eryk Sun added the comment: The narrow scope of this issue could be implemented by defining a scheme for local builds in the PythonCore key -- such as "X.Ys[-32]". The build process would create or update the "HKCU\Software\Python\PythonCore\X.Ys[-32]\InstallPath" key with the

[issue27602] Enable py launcher to launch repository Python.

2018-11-07 Thread Franklin Yu
Franklin Yu added the comment: Any updates? I would like to switch between versions of PyPy. -- nosy: +Franklin Yu ___ Python tracker ___

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Steve Dower
Steve Dower added the comment: > having two places for launcher configuration, the registry and the ini file, > seems like it would be confusing My hope here is that the registry is "the place where all your Pythons are registered" and py.ini is "the place where settings for py.exe are kept".

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Steve Dower
Steve Dower added the comment: I think this is best written as: * extend py.exe to handle PEP 514 properly * write "PythonCore\dev36" (or equivalent - maybe "PythonDev\dev36"?) keys on each build That way you could use "py -dev36" to get your latest build from source (actual tag open to

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Paul Moore
Paul Moore added the comment: On 23 July 2016 at 23:01, Eryk Sun wrote: >> I assume you wouldn't expect to support shebang lines >> like "#!python3.6r"? > > That's already supported in py.ini in the [commands] section, per PEP 397. True, I'd forgotten that. I was

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Eryk Sun
Eryk Sun added the comment: > I assume you wouldn't expect to support shebang lines > like "#!python3.6r"? That's already supported in py.ini in the [commands] section, per PEP 397. I've used this from Vinay's initial releases on Bitbucket, before the launcher was officially distributed with

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Zachary Ware
Zachary Ware added the comment: --register sounds interesting. It could write to the user-specific py.ini, and would be useful for other things, like for `py --register pypy C:\pypy\pypy.exe`. I've also thought it would be useful to be able to use py.exe directly to invoke interpreters

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Paul Moore
Paul Moore added the comment: This sounds like 2 related items (but I'm happy for them both to be under this issue, I'm not suggesting we need 2 issues): 1. Allowing py -register to add PEP 514 metadata to the registry for the given path. 2. Allowing py - to use PEP 514 metadata more

[issue27602] Enable py launcher to launch repository Python.

2016-07-23 Thread Terry J. Reedy
New submission from Terry J. Reedy: Running a repository build by typing a path such as F:\Python\dev\36\PCbuild\win32\python_d.exe is tedious and error prone and I have to remember to omit '\win32' for 2.7 and it takes up much of a command line. I would like to be able to run something like