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 minrk
Recipients dstufft, eric.araujo, minrk, pitrou, tdsmith
Date 2014-08-27.19:13:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
`--prefix` vs `--user` is the only conflict I have encountered, but based on the way it works, it could just as easily happen with any of the various other conflicting options in install (install_base, exec_prefix, etc.), though that might not be very common.

There is a general question: If a Python distributor wants sys.prefix and default install_prefix to differ, what's the right way to do it? Setting it in distutils.cfg makes sense other than the conflicting option issues. Could there be a special `default_prefix` key that gets used as the final fallback (end of install.finalize_unix)?

I would really like to avoid having a warning on every install, since warning suggests that something has been done incorrectly, which in turn suggests that `distutils.cfg` is the wrong place to set the install prefix.
Date User Action Args
2014-08-27 19:13:13minrksetrecipients: + minrk, pitrou, eric.araujo, dstufft, tdsmith
2014-08-27 19:13:13minrksetmessageid: <>
2014-08-27 19:13:13minrklinkissue22269 messages
2014-08-27 19:13:13minrkcreate