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 eryksun
Recipients eryksun, ezio.melotti, paul.moore, steve.dower, terry.reedy, tim.golden, vstinner, zach.ware
Date 2017-05-22.22:44:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495493066.35.0.0288158179961.issue30405@psf.upfronthosting.co.za>
In-reply-to
Content
Supporting PEP 514 tags is an interesting idea, but maybe you could go into more detail about what you have in mind. Are you thinking of using the SysVersion, SysArchitecture, and [Windowed]ExecutablePath fields where available instead of parsing version tags and assuming "python[w]/exe"? How would the expansion of candidate installations affect virtual "python" shebangs and command-line arguments such as -3.6-32? If there are several 32-bit 3.6 installations, which one wins?

The PY_PYTHON environment variable could support qualified tags such as "PythonDev/3.6-32". However, arbitrarily named tags can't be supported on the command line without introducing an option reserved for the launcher. It could look for an `X PY_PYTHON` option such as `py -X PY_PYTHON=PythonDev/3.6-32`. That's a bit verbose, but simpler than `cmd /c "set PY_PYTHON=PythonDev/3.6-32 & py`.
History
Date User Action Args
2017-05-22 22:44:26eryksunsetrecipients: + eryksun, terry.reedy, paul.moore, vstinner, tim.golden, ezio.melotti, zach.ware, steve.dower
2017-05-22 22:44:26eryksunsetmessageid: <1495493066.35.0.0288158179961.issue30405@psf.upfronthosting.co.za>
2017-05-22 22:44:26eryksunlinkissue30405 messages
2017-05-22 22:44:26eryksuncreate