Actually we can keep my venvs clean with a global env

Author: alexwlchan

README.md

@@ -21,15 +21,8 @@ To set up this repo on a new computer, I run the following commands in a Fish sh
     $ source .venv/bin/activate.fish
     $ pip install -r requirements.txt
     ```
-
-3.  Add some global pip config to [prevent installing anything outside virtual environments](https://blog.glyph.im/2023/08/get-your-mac-python-from-python-dot-org.html#and-always-use-virtual-environments):
-
-    ```console
-    $ mkdir -p ~/.pip
-    $ echo -e "[global]\nrequire-virtualenv = true" > ~/.pip/pip.conf
-    ```
     
-4.  Install my Fish config, so Fish knows where to find all these scripts:
+3.  Install my Fish config, so Fish knows where to find all these scripts:
 
     ```console
     $ ln -s ~/repos/scripts/config.fish ~/.config/fish/config.fish

config.fish

@@ -22,6 +22,17 @@ set -x fish_function_path ~/repos/scripts/fish_functions $fish_function_path
 fish_add_path /Library/Frameworks/Python.framework/Versions/3.12/bin
 
 
+# This prevents me from installing packages with pip without being
+# in a virtualenv first.
+#
+# This allows me to keep my system Python clean, and install all my
+# packages inside virtualenvs.
+#
+# See https://docs.python-guide.org/dev/pip-virtualenv/#requiring-an-active-virtual-environment-for-pip
+#
+set -g -x PIP_REQUIRE_VIRTUALENV true
+
+
 # This tells fish to run a couple of functions as event handlers --
 # that is, to run a function when a variable changes or something similar.
 # These functions can't be autoloaded.