[issue27064] Make py.exe default to Python 3 when used interactively

Changes by Zachary Ware : -- stage: patch review -> resolved ___ Python tracker ___

[issue27064] Make py.exe default to Python 3 when used interactively

Changes by Paul Moore : -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue27064] Make py.exe default to Python 3 when used interactively

Roundup Robot added the comment: New changeset 26c1e3dab624 by Paul Moore in branch 'default': Issue #27064: The py.exe launcher now defaults to Python 3. https://hg.python.org/cpython/rev/26c1e3dab624 -- nosy: +python-dev ___ Python tracker

[issue27064] Make py.exe default to Python 3 when used interactively

Paul Moore added the comment: OK, no problem. Like you say, not a high priority. -- ___ Python tracker ___

[issue27064] Make py.exe default to Python 3 when used interactively

Steve Dower added the comment: Unfortunately, the current MSI for the launcher doesn't have a great interface when used separately from the main installer. It happens to be more functional than the rest (i.e. double-clicking it will give you a very quick per-user install, whereas the other

[issue27064] Make py.exe default to Python 3 when used interactively

Paul Moore added the comment: Terry: Correct. As 3.4 is in security fix mode, and 2.7 doesn't come with the launcher (which I hadn't realised - thanks for pointing this out Zach!) the only real backport candidate is 3.5, so I definitely don't think it's worth backporting just for that.

[issue27064] Make py.exe default to Python 3 when used interactively

Terry J. Reedy added the comment: +1 By 'interactive use', I presume you mean at console command line path\to\somewhere>py... When I installed 3.4.4, I wondered if it would overwrite py with older version. Great that 3.5.x does not. I think each installer should have latest version of

[issue27064] Make py.exe default to Python 3 when used interactively

Zachary Ware added the comment: I'm very much +1 on the patch. A couple thoughts: - Note that 2.7 doesn't come with a launcher. - As I understand it, the 3.5+ installer won't overwrite a newer launcher than what it would install, but the 3.4- installer will. So the only really confusing (to

[issue27064] Make py.exe default to Python 3 when used interactively

Paul Moore added the comment: Thanks Ned. Personally, I'm still inclined *not* to add this to 2.7/3.5. People will get it when the install the 3.6 alphas, sure, but that seems to me to be a relatively obvious consequence of installing an alpha that includes a component that's used for all

[issue27064] Make py.exe default to Python 3 when used interactively

Ned Deily added the comment: 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

[issue27064] Make py.exe default to Python 3 when used interactively

Paul Moore added the comment: Because of the nature of the launcher, there's not much we can do about that IMO. And there was no real objection to changing the default on the python-ideas thread (at least for interactive use). But I'll wait to see if Ned has anything to add. --

[issue27064] Make py.exe default to Python 3 when used interactively

Steve Dower added the comment: It'll change their default behavior if they get an alpha release of 3.6 though, and uninstalling the alpha won't revert it. That said, I don't really feel like the launcher is an "alpha" product, even if the core Python engine is in that state. Possibly the RM

[issue27064] Make py.exe default to Python 3 when used interactively

Paul Moore added the comment: Thanks Steve. I wasn't sure over versioning, which is why I decided to be conservative. Also, it's probably not good to change the default behaviour on people when they just install a patch release of 3.5. -- ___

[issue27064] Make py.exe default to Python 3 when used interactively

Steve Dower added the comment: LGTM. The launcher is in a bit of a funny place wrt versioning, as it is now somewhat independent from the Python version it is installed with: * won't be downgraded by 3.5 (3.4 will still stomp over the file itself) * has a separate entry in Programs & Features

[issue27064] Make py.exe default to Python 3 when used interactively

New submission from Paul Moore: By default, the launcher tries to launch (the latest version of) Python 2 on the user's machine. This can be altered with the configuration file, and if the user doesn't have Python 2 installed Python 3 will be used. Now that we are at Python 3.6, it's about