The Set Up Environment Variables section of the README has this code:
cd backend
pip install -r requirements.txt
On Macs where python3 is managed by Homebrew, this leads to unexpected behavior. Homebrew intentionally takes over the python3 command but does not take over pip. As a result, the above command installs packages into the system Python environment, not the one invoked by python3:
➜ ~ which pip
/usr/local/bin/pip
➜ ~ which python3
/opt/homebrew/bin/python3
This mismatch caused bugs that prevented me from completing the workshop.
One possible fix is to recommend creating a virtual environment and using:
python3 -m pip install -r requirements.txt`
In my own workshops I've started using uv to simplify setup. After cloning the repo, students run:
This creates a virtual environment with the same Python version and package versions I used when altering the tutorial. Example: Streamlit Tutorial Setup.
The Set Up Environment Variables section of the README has this code:
cd backend pip install -r requirements.txtOn Macs where
python3is managed by Homebrew, this leads to unexpected behavior. Homebrew intentionally takes over thepython3command but does not take overpip. As a result, the above command installs packages into the system Python environment, not the one invoked bypython3:This mismatch caused bugs that prevented me from completing the workshop.
One possible fix is to recommend creating a virtual environment and using:
python3 -m pip install -r requirements.txt`In my own workshops I've started using
uvto simplify setup. After cloning the repo, students run:This creates a virtual environment with the same Python version and package versions I used when altering the tutorial. Example: Streamlit Tutorial Setup.