This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients Dude-X, jaraco, srid, ssbarnea
Date 2010-09-03.14:07:57
SpamBayes Score 1.8253147e-09
Marked as misclassified No
Message-id <>
The big problem with adding the %python%\scripts directory to the path is it makes a lot of assumptions about how Python is deployed.

And it raises some questions. What should the precedence be? What should happen if multiple versions of Python are installed? Should the latest version take precedence? Should the latest version remove the path for the previous version?

Personally, I'm -1 on this idea unless it's a checkbox that can easily be deselected (or not selected by default). I install multiple different versions of Python to my system and I symlink \Python to the "active" version and I add "\Python\Scripts" to the path, so I can easily switch between my active version of Python. Adding \Python26\Scripts and \Python26-64\Scripts and \Python27\Scripts and ... to the path could become very messy.

Perhaps a better solution would be to provide a link in the start menu or a script to be run which adds the scripts to the path for that instance of Python... so it could be easily and painlessly added after the fact.
Date User Action Args
2010-09-03 14:08:00jaracosetrecipients: + jaraco, Dude-X, ssbarnea, srid
2010-09-03 14:07:59jaracosetmessageid: <>
2010-09-03 14:07:58jaracolinkissue7231 messages
2010-09-03 14:07:57jaracocreate