Message140600
[Carl]
> there's an implicit assumption that a .pth file is the most likely
> strategy.
If you have other ideas, please share them.
[another message]
> I don't see why the installation-location-finding for develop should
> be any different than for a normal "pysetup install".
It’s only a technical limitation for now: the develop command is currently a standalone command, so it has to decide where to write stuff. If it were an option to install_dist instead of a standalone command, then it would have paths processing already written.
Higery changed his code recently to get paths from the install_dist command instead of requiring site-packages. (You can read the reviews, if you don’t mind style comments mixed with more important issues.)
> Does "pysetup install" install to global site-packages by default, or
> try to find somewhere it can install without additional privileges?
The install action can have a different behavior than the install_dist command. develop is only a command now, and I agree it should behave like install_dist (which it now does).
> (though I don't really see the value in "arbitrary locations", since
> you then have to set up PYTHONPATH manually anyway).
We don’t know what people do, what with /opt installs and plugins and whatever, so there’s just no value in not allowing any path for install.
> Certainly "develop" should support PEP 370, ideally with the same
> command-line flag as a regular install.
Yes. |
|
Date |
User |
Action |
Args |
2011-07-18 16:18:47 | eric.araujo | set | recipients:
+ eric.araujo, tarek, carljm, meatballhat, Peter.Waller, alexis, michael.mulich, higery |
2011-07-18 16:18:46 | eric.araujo | set | messageid: <1311005926.87.0.271612716216.issue8668@psf.upfronthosting.co.za> |
2011-07-18 16:18:46 | eric.araujo | link | issue8668 messages |
2011-07-18 16:18:45 | eric.araujo | create | |
|