On Sun, 13 Apr 2025 19:10:47 -0400, Jonathan Gossage wrote:
> The version of Python was compiled from source code and installed with
> make altinstall. I attempted to use *pip* to install the *Sphinx*
> package into the virtual environment using the command *pip install
> sphinx* in the virtual en
Please include the group in your response; don't just send it to me.
On 4/14/2025 5:09 AM, Jonathan Gossage wrote:
The virtual environment was owned by the user running pip. It was not
owned by root. Does pip not support virtual environments that are owned
by a non-root user and have a multi-us
On 4/14/2025 6:20 PM, Keith Thompson via Python-list wrote:
Thomas Passin writes:
[...]
To activate a venv, you have to source its activate script, which is
in the venv. First you have to mark it as executable. Then you source
it -
source ~/venv/gf4/bin/activate
[...]
No, you don't have to
On 4/14/2025 6:20 PM, Keith Thompson via Python-list wrote:
Thomas Passin writes:
[...]
To activate a venv, you have to source its activate script, which is
in the venv. First you have to mark it as executable. Then you source
it -
source ~/venv/gf4/bin/activate
[...]
No, you don't have to
Thomas Passin writes:
[...]
> To activate a venv, you have to source its activate script, which is
> in the venv. First you have to mark it as executable. Then you source
> it -
>
> source ~/venv/gf4/bin/activate
[...]
No, you don't have to (and probably shouldn't) mark the script as
executable.
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 p
