[00:06:23] <njs> lifeless: how confident are you that the --root and --target arguments defined for ``develop`` in your draft cover all the cases that pip actually uses?
[00:06:56] <lifeless> I derived them looking at the function calls in pip
[00:07:06] <lifeless> so, while I don't recall the code this second, fairly.
[00:07:27] <njs> --user and --home are special cases of --prefix?
[00:14:57] <lifeless> njs: mmm, brain is failing. I think I need to hunt food
[00:50:46] <njs> oh, the difference between --home=$DIR and --prefix=$DIR is that --home=$DIR installs into $DIR/lib/python, while --prefix=$DIR installs into $DIR/lib/pythonX.Y/site-packages/
[00:51:26] <njs> and pip install --target=$DIR maps to --home=$DIR
[00:52:46] <njs> .....except this is wrong, because pip install --target=$DIR actually just drops the python files into $DIR, so I'm misreading something somewhere. wtf.
[01:15:47] <njs> lifeless: I think my conclusion from all of this is (a) screw it, technically --prefix is not quite a replacement for all possible install settings, but the only *useful* things to pass to install -e are --prefix= and --root= and --user, and all of those are covered. (b) in fact we can simplify by just making the --prefix mandatory, and make it the only option provided -- everything else including --root can be folded into it.