[issue24306] Backport py.exe to 3.4

2015-11-07 Thread Roundup Robot
Roundup Robot added the comment: New changeset 6181476b5534 by Steve Dower in branch '3.4': Issue #24306: Sets component ID for launcher to match 3.5 and later to avoid downgrading. https://hg.python.org/cpython/rev/6181476b5534 -- nosy: +python-dev

[issue24306] Backport py.exe to 3.4

2015-11-07 Thread Steve Dower
Changes by Steve Dower : -- assignee: -> steve.dower resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue24306] Backport py.exe to 3.4

2015-11-02 Thread Steve Dower
Steve Dower added the comment: So with the 3.5 launcher being installed all-users by default, the attached patch is a good option. I'm not able to build 3.4 entirely, but I made the modification to the MSI directly and it works fine, so I intend to go ahead and apply it (with some extra line

[issue24306] Backport py.exe to 3.4

2015-06-20 Thread Steve Dower
Steve Dower added the comment: Attached a patch to set the component IDs in the 3.4 installer to match the ones we're using for 3.5 and later. This should prevent downgrading of the launcher in future releases, though it's not strictly the right way to do this. (Nosied Martin in case he wants

[issue24306] Backport py.exe to 3.4

2015-06-20 Thread Larry Hastings
Larry Hastings added the comment: Last installed wins isn't perfect, but at least it's predictable. Is it possible to make the 3.4 installer detect that 3.5+ is installed and not install the launcher? -- ___ Python tracker rep...@bugs.python.org

[issue24306] Backport py.exe to 3.4

2015-05-28 Thread Mark Lawrence
Mark Lawrence added the comment: I don't see removing the launcher as an option. So how about do the backport and make certain it's well documented in the release notes and here https://docs.python.org/3/using/windows.html ? If anyone has a better idea feel free to fire away. --

[issue24306] Backport py.exe to 3.4

2015-05-27 Thread Steve Dower
New submission from Steve Dower: For 3.5 32-bit installs we register in a different key to avoid collisions with 64-bit installs, but now the 3.4 launcher can't find us. If you have installed 3.4 for all users (likely) and then install 3.5 just-for-me (also likely), then you'll continue to

[issue24306] Backport py.exe to 3.4

2015-05-27 Thread Steve Dower
Steve Dower added the comment: I didn't mention it initially, but the harm it can do is overriding newer versions. The 3.5 and later installers have proper versioning built in, but I don't think that's possible with the 3.4 installer as well (due to MSI limitations, not any deficiency of the

[issue24306] Backport py.exe to 3.4

2015-05-27 Thread Mark Lawrence
Mark Lawrence added the comment: Can it actually do any harm? It certainly appears to remove the potential for a lot of bug reports from a lot of frustrated users, myself included. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org