<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-AU>Checking the Version (!=SysVersion) property should be enough (and perhaps we need to set it properly on install). The launcher currently only works with PythonCore entries anyway, so no need to worry about other distros.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>PEP 514 allows for other keys to be added as well (it specifies a minimum set), so we could just set one for this. “NoDefaultLaunch” or similar.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>Finally, if someone created a script for setting py.ini, it could probably be included in the Tools directory. Wouldn’t be run on install or get a start menu shortcut though, just to set expectations right.</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Top-posted from my Windows phone</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:p.f.moore@gmail.com">Paul Moore</a><br><b>Sent: </b>Wednesday, February 7, 2018 7:37<br><b>To: </b><a href="mailto:tritium-list@sdamon.com">Alex Walters</a><br><b>Cc: </b><a href="mailto:python-ideas@python.org">Python-Ideas</a><br><b>Subject: </b>Re: [Python-ideas] Possible Enhancement to py Launcher - set default</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I don't think so. As an example, what registry keys would Anaconda</p><p class=MsoNormal>write to say that Release 5.2.1.7 is a pre-release version? Or would</p><p class=MsoNormal>the py launcher have to parse the version looking for rc/a/b/... tags?</p><p class=MsoNormal>And distributions would have to agree on how they record pre-release</p><p class=MsoNormal>version numbers?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Paul</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 7 February 2018 at 14:57, Alex Walters <tritium-list@sdamon.com> wrote:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>>> -----Original Message-----</p><p class=MsoNormal>>> From: Paul Moore [mailto:p.f.moore@gmail.com]</p><p class=MsoNormal>>> Sent: Wednesday, February 7, 2018 4:15 AM</p><p class=MsoNormal>>> To: Alex Walters <tritium-list@sdamon.com></p><p class=MsoNormal>>> Cc: Steve Barnes <gadgetsteve@live.co.uk>; Python-Ideas <python-</p><p class=MsoNormal>>> ideas@python.org></p><p class=MsoNormal>>> Subject: Re: [Python-ideas] Possible Enhancement to py Launcher - set</p><p class=MsoNormal>>> default</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>> ...</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> IMO the biggest technical issue with this is that as far as I can see</p><p class=MsoNormal>>> PEP 514 doesn't specify a way to determine if a given Python is a</p><p class=MsoNormal>>> pre-release version. If we do want to implement this (I'm +0 on it,</p><p class=MsoNormal>>> personally) then I think the starting point would need to be an update</p><p class=MsoNormal>>> to PEP 514 to include that data.</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> Paul</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Looking at pep 514, it looks like sys.winver is what would have to change to support reporting the release status to the registry. I don't think 514 has to change at all if sys.winver changes. Is that a correct interpretation?</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>Python-ideas mailing list</p><p class=MsoNormal>Python-ideas@python.org</p><p class=MsoNormal>https://mail.python.org/mailman/listinfo/python-ideas</p><p class=MsoNormal>Code of Conduct: http://python.org/psf/codeofconduct/</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>