From 2f7621b88919bae4b2833f474e35a03a9543007c Mon Sep 17 00:00:00 2001
From: Alexander Grund <alexander.grund@tu-dresden.de>
Date: Fri, 8 Mar 2024 12:29:56 +0100
Subject: [PATCH] Add instructions for using `EB_PYTHON`

---
 .../software/custom_easy_build_environment.md | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/doc.zih.tu-dresden.de/docs/software/custom_easy_build_environment.md b/doc.zih.tu-dresden.de/docs/software/custom_easy_build_environment.md
index 02b7c4bab..1a2dbe0b4 100644
--- a/doc.zih.tu-dresden.de/docs/software/custom_easy_build_environment.md
+++ b/doc.zih.tu-dresden.de/docs/software/custom_easy_build_environment.md
@@ -239,3 +239,27 @@ It might also be helpful to use
 ```console
 marie@compute$ export LMOD_IGNORE_CACHE=0
 ```
+
+(Especially) when you want to use additional features of EasyBuild, such as the
+[GitHub integration](https://docs.easybuild.io/integration-with-github/),
+ you might need to set a specific Python version to use by EasyBuild.
+
+That is unrelated to any Python module you might wish to use or install!
+Furthermore, when using EasyBuild you should **not** have any other modules loaded,
+not even `Python`.
+
+Which Python executable is used by EasyBuild can be shown by executing:
+
+```console
+marie@compute$ EB_VERBOSE=1 eb --version
+```
+
+You can change it by setting `EB_PYTHON`, e.g.:
+
+```console
+marie@compute$ export EB_PYTHON=python3.8
+```
+
+In case you are using a virtualenv for use with EasyBuild
+then using `python` instead of `python3.8` or similar is enough
+as there will be a `python` binary available inside your virtualenv.
-- 
GitLab