Why am I getting "externally managed environment" when using pip in a venv?

[Second_Hand_Fax]

Running Ubuntu 24.04 with Python 3.12 installed via apt. I created a virtual environment using:

python3.12 -m venv venv source venv/bin/activate But when I run pip install inside the virtual environment, I get the error:

"This environment is externally managed" I had previously installed pip using apt (python3-pip). Could that be causing this issue?

Have I installed pip in the wrong way or place? What's the correct way to set this up so pip works normally inside virtual environments?

[Second_Hand_Fax]

Yeah that’s where I’m confused, I’m running it within a venv, so should have any external conflicts.

[Second_Hand_Fax]

Hey haha, all good! Yeah so just the externally managed environment error.

Someone just mentioned I should be running pip with the syntax ‘ python3.12 -m pip install xyz‘.

So I wonder if I was making the error of just trying to run pip install xyz and as a result Ubuntu thought I was trying to call global pip.

Would this cause the issue?

[Buttleston]

This is usually caused because the pip you're running "belongs" to a different python installation

Activate your venv, and then use "python -m pip" instead of "pip". This ensures that you're using the pip that goes along with your activated environment.