Hi, On 15 March 2015 at 14:06, Mads Kiilerich <[email protected]> wrote: >> It really does work, it installs packages into ~/.local, which is >> useful if you just want to test things out, and if you do want to mix >> your system packages with locally installed ones.
> How does it work? Will the global installation of pip hook into Python > startup and inject packages from .local in sys.path? How about executable > scripts - where are they placed? I think it's present there always. At least, I don't need to specify any option to load packages from ~/.local. Executable scripts are installed into ~/.local/bin. > Either way, I understand that pip --user still will install the packages in > a shared location. That will make it very hard to uninstall or "start over". > I guess it also makes it impossible for the a user to have more than one > Kallithea instance. It is very easy to do that. Just drop ~/.local, switch to another user or anything like that. > I think we need more clarification of pros and cons of the different options > before we start recommending more options. > > In my opinion, virtualenv is the only _real_ option. It makes pip simple and > managable so we know exactly where the dependencies for this app is > installed. Running pip without virtualenv (with or without --user) can > easily create situations that are very hard to recover from. I'm not a Python pro, but somehow I managed to never run into them :) -- Cheers, Andrew _______________________________________________ kallithea-general mailing list [email protected] http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
