14 Sep
2018
14 Sep
'18
8:09 a.m.
On Fri, 14 Sep 2018 at 08:16, Alex Becker
Is there a way around this behavior? Am I crazy to even try to install into a different virtualenv? Or do I have to re-architect my code to call pip in the target virtualenv (which may require me forcing pip to be installed, depending on what versions of python I choose to support)?
The simple answer here is that this isn't something that pip supports, nor is it something that anyone has ever considered adding support for. So you're basically on your own if you want to avoid using the pip in the target virtualenv. Paul