Copy the python used to create the venv into the venv itself

This is now safe, because when python on the system gets updated, we detect the change and rebuilds the Python-modules.
alisw · Jan 8, 2025 · 89f7c2d · 89f7c2d
1 parent 6974f52
commit 89f7c2d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/python-modules.sh b/python-modules.sh
@@ -24,7 +24,7 @@ unset VIRTUAL_ENV
 # NOTE: If you get an error saying "Error: This build of python cannot create
 # venvs without using symlinks", then you are using the MacOS Python. You
 # should be using the Homebrew Python instead, so run "brew install python".
-python3 -m venv "$INSTALLROOT"
+python3 -m venv --copies "$INSTALLROOT"
 . "$INSTALLROOT/bin/activate"
 # From now on, we use the python3 binary copied into the venv. This makes pip
 # install packages into the venv.