Author ned.deily
Recipients ned.deily, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-05-20.19:33:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463772823.54.0.489842887669.issue27064@psf.upfronthosting.co.za>
In-reply-to
Content
I don't have a strong opinion one way on the matter since I don't have any experience with the launcher.  I think I understand the issue of the Windows installer providing "release-independent" components (and, FTR, the OS X installer has a somewhat similar issue although the launcher there is believed to not be used much at all).  Whether we should change the defaults for future releases of 2.7.x and/or 3.5.x is probably ultimately up to the 2.7 and 3.6 release managers though I expect they would go along with whatever you all recommend.  If it does make sense to modify py.exe for 2.7.x and 3.5.x, then perhaps the corresponding change for 3.6 could be deferred until after 2.7.11 and 3.5.2 are released, which should be before 3.6.0a3, and all have consistent documentation of the changed behavior?  It's not perfect but at least all of the most recent binary releases would be consistent.

A somewhat unrelated comment on the patch:  will it be clear to users what is meant by "latest version installed"?  That is, what is meant by "latest version" in each of these cases: (scenario 1) install 2.7. then 3.5, then 3.6'; (scenario 2) install 3.5, 3.6, then 2.7; (scenario 3) install 3.6, 3.5, then 2.7; (scenario 4) install 3.6, 2.7, then 3.5.
History
Date User Action Args
2016-05-20 19:33:43ned.deilysetrecipients: + ned.deily, paul.moore, tim.golden, zach.ware, steve.dower
2016-05-20 19:33:43ned.deilysetmessageid: <1463772823.54.0.489842887669.issue27064@psf.upfronthosting.co.za>
2016-05-20 19:33:43ned.deilylinkissue27064 messages
2016-05-20 19:33:43ned.deilycreate