Message226004
| 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 |
<1409166793.79.0.754373993597.issue22269@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
`--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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年08月27日 19:13:13 | minrk | set | recipients:
+ minrk, pitrou, eric.araujo, dstufft, tdsmith |
| 2014年08月27日 19:13:13 | minrk | set | messageid: <1409166793.79.0.754373993597.issue22269@psf.upfronthosting.co.za> |
| 2014年08月27日 19:13:13 | minrk | link | issue22269 messages |
| 2014年08月27日 19:13:13 | minrk | create |
|