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 eric.araujo
Recipients Peter.Waller, alexis, carljm, eric.araujo, higery, meatballhat, michael.mulich, tarek
Date 2011-07-12.14:48:16
SpamBayes Score 9.050702e-06
Marked as misclassified No
Message-id <>
I’ve reviewed the last patch.  It looks like the code only installs to the global site-packages, and there is no support to install to the user site-packages or to another arbitrary location.

On Windows, normal users seem to be able to write to the global site-packages (see #12260), but on other OSes with a proper rights model <wink> that won’t do.  Luckily, PEP 370 brings us user site-packages (currently poorly documented, see #8617 and #10745), but only for 2.6, 2.7 and 3.x.  It looks like Tarek is ready to drop 2.4 compatibility for distutils2, so the question is: what to do under 2.5?

Generally, I don’t see why develop could not install to any directory.  We want a default invocation without options to Just Work™, finding a writable directory already on sys.path and writing into it, but that doesn’t exclude letting the user do what they want.
Date User Action Args
2011-07-12 14:48:17eric.araujosetrecipients: + eric.araujo, tarek, carljm, meatballhat, Peter.Waller, alexis, michael.mulich, higery
2011-07-12 14:48:17eric.araujosetmessageid: <>
2011-07-12 14:48:16eric.araujolinkissue8668 messages
2011-07-12 14:48:16eric.araujocreate