Python3, Python, Pip, Pip3, Homebrew And .Venv

/ all-scribbly / By

All correct – just use pip3 to install packages into homebrew python + Use a venv

spiffy@shawneee-mini  ~  which python
python: aliased to python3

spiffy@shawneee-mini  ~  which python
python: aliased to python3

spiffy@shawneee-mini  ~  which python3
/opt/homebrew/bin/python3

spiffy@shawneee-mini  ~  which pip
/Library/Frameworks/Python.framework/Versions/3.12/bin/pip

spiffy@shawneee-mini  ~  which pip3
/opt/homebrew/bin/pip3

Always use a venv with python now

python3 -m venv ~/.venv
source ~/.venv/bin/activate
pip3 install beautifulsoup4 
# can be pip if in venv 
# Run your scripts here

you will avoid all the newer Homebrew/Python restrictions and PEP 668 issues, and your package installations will never interfere with system or Homebrew-managed Python.

Benefits:

  • Every package install via pip goes ONLY into the active venv—never affects system Python or Homebrew Python managed packages.
  • You avoid “externally-managed-environment” errors.
  • All scripts you run while the venv is active will “see” the packages you’ve pip-installed in that venv.

Summary:

  • venv is now “the right way” for Python on Macs, especially with Homebrew Python.
  • No more system-wide package conflicts or permission headaches.
  • If you have multiple projects, you can have a venv per project, or just use one venv for all your scripting if you’re happy with a single shared environment.

You’ll have a smoother experience and all your dependency management will “just work”!

why ~/.venv

  • ALWASYS usign .venv makes it easier acroos difffetn machine etc. they do not sync unless yyou do it manually

  • If you run python3 -m venv .venv, it creates a hidden .venv directory in the current folder.

    • Use this if you want a per-project venv (Python community best practice for app/dev repos).

  • If you run python3 -m venv ~/.venv, it creates a hidden .venv directly in your home directory.

    • This acts as a “universal” venv for all your scripts on that computer (for your user). You can activate this venv from any directory:

      bash
source ~/.venv/bin/activate

    • All packages installed in this venv are available whenever it is activated, regardless of your working directory.

    • Only one universal venv is needed per machine unless you want project-specific environments.

Summary:

  • .venv (no slash) = venv in “this” directory (good for per-project).
  • ~/.venv = venv in your user home directory (system-wide for just you).

Choose whichever matches your workflow:

  • Multiple projects / repos: Use .venv per project.
  • Personal utilities/one global: Use ~/.venv for a “global per-user” venv.

Either way, you’re set for conflict-free Python scripting!

pip and pip3 in and out of venv

When you are inside a venv (activated), you can use either pip install beautifulsoup4 or pip3 install beautifulsoup4—they both target the venv’s pip and install correctly.

  • While the venv is activated, the pip and pip3 commands are both symlinked in the venv’s bin directory and point to the same executable.
  • You do not have to worry about mixing system pip and venv pip during an active venv session.

But:

  • If you are NOT in a venv, always use pip3 (not bare pip) to avoid accidentally installing to the wrong Python environment (especially on macOS/Homebrew).

Summary:

  • In a venv: pip install ... or pip3 install ... — both are safe and correct.
  • Globally (outside venv): Only use pip3 (not just pip) on macOS so you don’t hit the system Python.
  • If ever unsure, you can always run python3 -m pip install beautifulsoup4.

Inside a venv, both pip and pip3 are “the right one.”
You’re safe!

Not great other metods

Yes, if you switched your preferred Python to Homebrew’s /opt/homebrew/bin/python3, you should reinstall any Python packages (like beautifulsoup4) for that interpreter, as each Python install maintains its own site-packages.

What to do:

  1. Make sure you are using Homebrew Python:

    bash
which python3
# Should print: /opt/homebrew/bin/python3

  2. Install beautifulsoup4 using Homebrew Python’s pip (not the global/system pip):

    bash
/opt/homebrew/bin/python3 -m pip install beautifulsoup4

  3. If you use a venv, activate it first, and then run:

    bash
pip install beautifulsoup4

    This ensures the package is installed for the correct Python interpreter.

Summary:

  • You do not need to reinstall Python itself, just the packages for your preferred interpreter.
  • Always use the pip/version matching the Python interpreter you will actually use for scripting.

Run python3 -m pip install beautifulsoup4 and you’ll be all set on the Homebrew Python install! If you use venv in the future, activate and re-install as needed inside the venv.

Venv with Homebrew Python

Here are the steps to use a venv with Homebrew Python (or any Python 3.x):

  1. Navigate to your project directory (wherever your clean_html.py is, or wherever you want your venv):

    bash
cd /path/to/your/project

  2. Create a virtual environment:

    bash
python3 -m venv venv

    (This creates a folder named venv in your project directory.)

  3. Activate the venv:

    • On macOS/Linux:

      bash
source venv/bin/activate

    • On Windows:

      text
venv\Scripts\activate

  4. Install required packages inside the venv:

    bash
pip install beautifulsoup4

  5. Run your script (while venv is active):

    bash
python clean_html.py /path/to/file.html

  6. When done, deactivate venv (optional but good practice):

    bash
deactivate

Notes:

  • While the venv is active, any Python or pip command will use packages isolated in that venv.
  • You never need sudo for pip inside venv—everything is local to your project.
  • If you ever erase/restart the venv, just recreate and reinstall your packages.

Summary:

  • venv makes package and Python version management bulletproof and project-specific.
  • Activate the venv every time you want to work in that project.

Let me know if you need more help with venv basics or Mac specifics!

All aliases are correct

Correct: You do NOT want to alias pip → pip3 (or vice versa) because:

  • Your python is Homebrew Python (/opt/homebrew/bin/python3), but your pip is the system Python 3.12 in /Library/Frameworks/.

  • If you alias pip to pip3, you risk masking/cutting off the system-installed pip (which may be used by some tools/scripts/Apple stuff).

  • Instead, always use the explicit pip3 for Homebrew Python, and/or use:

    bash
python3 -m pip install beautifulsoup4

    or

    bash
/opt/homebrew/bin/python3 -m pip install beautifulsoup4

Why this matters:

  • Your Homebrew Python and /Library/Frameworks/ Python are two completely separate Python installations, each with their own set of packages.
  • Using the right pip keeps your packages in the right place.

Summary:

  • Do NOT alias pip to pip3—just use pip3 for Homebrew Python or python3 -m pip ... always.
  • This way, you keep Homebrew Python and its pip as your preferred Python environment for personal/dev scripting.
  • Leave the system pip untouched for system/global use.

If you want everything to default to Homebrew, update your PATH so /opt/homebrew/bin is BEFORE /Library/Frameworks/Python.framework/... in your shell config—then python3 and pip3 will “just work” everywhere.
But explicitly, always use pip3 and python3 to guarantee you’re in the right world!

Related Posts