From 89f7c2db8842b8b15fc92f8e2c0cf5cf31b9deb4 Mon Sep 17 00:00:00 2001
From: Giulio Eulisse <10544+ktf@users.noreply.github.com>
Date: Wed, 8 Jan 2025 10:44:58 +0100
Subject: [PATCH] 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.
---
 python-modules.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python-modules.sh b/python-modules.sh
index 5b0daf4118..06556e5029 100644
--- 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.