[issue8357] Add a --show-installation-paths in the install command

Changes by Éric Araujo : -- resolution: accepted -> out of date stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___

[issue8357] Add a --show-installation-paths in the install command

Changes by Éric Araujo : -- versions: +3rd party -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue8357] Add a --show-installation-paths in the install command

Éric Araujo added the comment: Assigning to myself. Not sure if I’ll do the logging idea Tarek suggested or an option to the configure command (#8252). -- assignee: tarek -> merwok stage: -> needs patch type: behavior -> feature request versions: +Python 2.5, Python 2.7, Python 3.2 _

[issue8357] Add a --show-installation-paths in the install command

Changes by Dan Buch : -- nosy: +meatballhat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8357] Add a --show-installation-paths in the install command

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue8357] Add a --show-installation-paths in the install command

Tim Kersten added the comment: Such an option would be useful indeed. An idea, though perhaps it's overkill, would be to show the current values of the options causing problems, specifically if they come from a config file or environment variable. i.e. when setup.cfg contains home=/somewhere

[issue8357] Add a --show-installation-paths in the install command

Tarek Ziadé added the comment: Ooops you are right, I messed up too in my explanation, I mischecked the code. root and home are mutually exclusive, not root and prefix. In any case, all those options are making it really hard to understand. I'd like to make this story easier in distutils2,