Author steve.dower
Recipients eryksun, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2016-07-24.03:46:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469331999.24.0.510569449395.issue27602@psf.upfronthosting.co.za>
In-reply-to
Content
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 bikeshedding).

Right now we write "python.bat" in the root of the source directory for the most recent build, so maybe that's a good enough workaround?

While I'd like to enable a "register" command, it's complicated enough and I suspect of limited value compared to directly editing the registry (or updating other interpreter's installers) that I'd rather not worry. A big part of the reason for PEP 514 is to be able to point other interpreters to it and say "do this and your users won't need to know where you installed everything".
History
Date User Action Args
2016-07-24 03:46:39steve.dowersetrecipients: + steve.dower, terry.reedy, paul.moore, tim.golden, zach.ware, eryksun
2016-07-24 03:46:39steve.dowersetmessageid: <1469331999.24.0.510569449395.issue27602@psf.upfronthosting.co.za>
2016-07-24 03:46:39steve.dowerlinkissue27602 messages
2016-07-24 03:46:38steve.dowercreate