Pip installs to unexpected place

[Keith Thompson]

rbowman <bowman at montana.com> writes:
> On Mon, 14 Apr 2025 09:55:09 -0400, Thomas Passin wrote:
>> Pip doesn't know about the environment it runs in. It seems to me that
>> you didn't active the venv before you installed using pip. So nothing
>> would have gotten installed into the venv. So where is the venv that you
>> set up? I usually put them into ~/venv. For example, a venv named "gf4"
>> is at ~/venv/gf4.
>
> Are you sure about that?

Sure about what?

>                          activate has
>
>
> VIRTUAL_ENV="/home/rbowman/work/python/weather"
> export VIRTUAL_ENV
[...]

The activate script is created when you create the venv (using something
like `python3 -m venv /path/to/new/venv`), and it's customized with the
location of the venv.

If Thomas creates a venv in ~/venv/gf4, that's what will appear in his
venv's active script (with the ~ expanded to the path of his home
directory).

(I'm relatively new at this.  Please let me know if I've gotten any of
the details wrong.)

[...]

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u at gmail.com
void Void(void) { Void(); } /* The recursive call of the void */