Re: pip installing scripts into another virtualenv

Yes, why not simply invoke the pip installed in the virtualenv into
which you want to install the packages? It doesn't seem like you'd
need to "re-architect" anything insomuch as simply change "pip" in
your argument list to the path to the pip inside the virtualenv you're
targeting.

--Chris

On Fri, Sep 14, 2018 at 12:15 AM, Alex Becker <[email protected]> wrote:
> As part of a package management tool, I'm trying to use pip to install
> python packages into a virtualenv, from python code (via subprocess), into a
> different virtualenv than the virtualenv my python process is running in (if
> any). I have this *mostly* working with:
>
> pip install --prefix [virtualenv-path] --ignore-installed
> --no-build-isolation
>
> However, installed scripts break because the scrips automatically get
> prepended with a shebang pointing to the python interpreter pip was run
> under.
>
> 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)?
>
> Sincerely,
>
> Alex Becker
>
> --
> Distutils-SIG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
> Message archived at
> https://mail.python.org/mm3/archives/list/[email protected]/message/C5Y2KKW2YQGFE74LZXQLXE32RJOABVEE/
>
--
Distutils-SIG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/DOY4US5P5GNMKVVHYMU6L5QQY6ZBH52E/