[issue9228] Make changes in the PATH and PATHEXT on installation

Nick Coghlan added the comment: If it is being requested every few months, then we should reconsider rejecting it. I have now reopened #3561 instead of this one. -- ___ Python tracker _

[issue9228] Make changes in the PATH and PATHEXT on installation

Éric Araujo added the comment: This is rejected every few months by Martin. -- nosy: +eric.araujo resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Windows installer should add Python and Scripts directories to the PATH environment variable

[issue9228] Make changes in the PATH and PATHEXT on installation

Changes by Jonathan Hartley : -- nosy: +jonathan.hartley ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9228] Make changes in the PATH and PATHEXT on installation

Nick Coghlan added the comment: That's not correct - we've merely pointed out that it isn't as easy as most people seem to think. For the POSIX world, there is a version management scheme based on symlinks in /usr/bin (or /usr/local/bin) and it is easy to add and remove entries independently

[issue9228] Make changes in the path and pathext on installation

R. David Murray added the comment: Modifying the path has be definitely rejected by python-dev. I don't know enough about windows to comment on the other two, but I suspect that everything that it is reasonable to do automatically is already being done. -- nosy: +loewis, r.david.murr

[issue9228] Make changes in the path and pathext on installation

New submission from ipatrol : I was fiddling around with easier ways to run python scripts in the Windows shell. I'll represent these as hypothetical AUTOEXEC.BAT entries (I used the UI for this): ;Add python to the search path so "python script.py" works set path="%path%;C:\Python27" ;Add .py