[issue14302] Move python.exe to bin/

Changes by Atsuo Ishimoto : -- nosy: +ishimoto ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14302] Move python.exe to bin/

Brian Curtin added the comment: > Additionally, the current Path-adding installer handles uninstallation. -- ___ Python tracker ___ _

[issue14302] Move python.exe to bin/

John Ehresman added the comment: Does this mean that the PATH entry won't be removed on uninstall? I can't tell from reading #3561, though I may have missed something. My worries are about the developer who doesn't know what the PATH is and would find it difficult to diagnose any problems c

[issue14302] Move python.exe to bin/

Brian Curtin added the comment: On 2 and 4, see #3561 for that discussion. A short answer would be that we're consenting adults. Additionally, the current Path-adding installer handles uninstallation. -- ___ Python tracker

[issue14302] Move python.exe to bin/

John Ehresman added the comment: Just a few thoughts from someone who uses Windows and who'd need to change code for this change: 1) I don't know if waiting to 3.5 is needed. I can make the change to look in the bin directory fairly quickly. 2) Is it safe to add scripts to the PATH? I'd wo

[issue14302] Move python.exe to bin/

Glenn Linderman added the comment: msg156410 sounds good to me... +1 If the conversion is optional in 3.3, that would seem to solve the problem; if BinaryDir is added, people can use that for 3.3; if people want to use software that hasn't migrated yet, they choose the default path of least r

[issue14302] Move python.exe to bin/

Martin v. Löwis added the comment: I'm still opposed to having the path manipulated by default, but Brian is working on a patch to edit the path with the default being off. If python.exe stays in the toplevel directory, it means that two entries have to be added to the path, making it even mo

[issue14302] Move python.exe to bin/

VanL added the comment: As Éric mentioned, there are two proposals here: 1. Move the python exe 2. Change 'Scripts' to 'bin' As for #1, what about letting the location of the python binary be an install option: [ ] Put python.exe into binaries directory and add to PATH? And then make it unc

[issue14302] Move python.exe to bin/

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue14302] Move python.exe to bin/

Martin v. Löwis added the comment: After more discussion, it appears that this change is too incompatible to be done in a single release. Therefore, I propose a long-term change into this direction, with the actual change not happening until 3.5. For the change of the python.exe location, I

[issue14302] Move python.exe to bin/

Martin v. Löwis added the comment: I'm still in favor of the change, accepting any breakage that will result from it. -- ___ Python tracker ___

[issue14302] Move python.exe to bin/

Brian Curtin added the comment: A suggested solution to that was to add BinaryPath to give them the proper path. We could potentially expose BinaryPath in older installers, just pointing at the same value as InstallPath. It's an installer-only change and very low (no?) risk, just preparing us

[issue14302] Move python.exe to bin/

Mark Hammond added the comment: Tools that use the registry will typically look up the InstallPath key and look for python.exe there. They will not look in sub-directories (except some may look in PCBuild and PCBuild/amd64). It is exactly those tools I'm concerned about. -- __

[issue14302] Move python.exe to bin/

Brian Curtin added the comment: It'll break tools who just look for "C:\\Python%d%d\python.exe" % (x, y) or some variation, but that's not a very dependable solution. If you're using the registry to find actual install locations, I think you'll be alright. What other solutions for finding pyt

[issue14302] Move python.exe to bin/

Mark Hammond added the comment: To clarify the second comment from Eric: it is actually the first of the proposals that I consider controversial - moving where python.exe lives (regardless of to where) will break 3rd party tools. If a decision was made to move it anyway, then renaming "Scrip

[issue14302] Move python.exe to bin/

Brian Curtin added the comment: If that thread ever comes to a conclusion, can someone summarize it here? Also, is there a reason distutils even matters here? -- ___ Python tracker ___

[issue14302] Move python.exe to bin/

Éric Araujo added the comment: IIUC this is about two changes: - Moving python.exe to the scripts subdirectory instead of the top-level install dir - Renaming that subdir from Scripts to bin The first change will reduce the number of dirs to add to PATH from two to one, which sounds nice; the

[issue14302] Move python.exe to bin/

New submission from Brian Curtin : After talks at PyCon with several people, python.exe will live in C:\Python33\bin rather than C:\Python33 to come more in line with the Unix layout. This will also simplify another issue with the Path option for the 3.3 installer as well as packaging's targe