Fix the detection of an unhappy installation path in a venv under Windows

External tools like VSCode can modify the case of the path saved in `sys.executable`

Author: Thierry RAMORASOAVINA

CHANGELOG.md

@@ -13,6 +13,7 @@
 
 ### Fixed
 - (`sklearn`) Default value of `n_features` for the supervised estimators
+- (`core`) Detection of an unhappy installation path in a venv under Windows
 
 ## 11.0.0.2 - 2026-01-26
 

khiops/core/internals/runner.py

@@ -1240,11 +1240,17 @@ def _detect_library_installation_incompatibilities(self, library_root_dir):
                         # Under Windows, there are two cases :
                         (
                             # for conda-based installations python is inside 'base_dir'
-                            str(Path(sys.executable).parents[0]) != base_dir
+                            # (warning : the case of the path in sys.executable
+                            # can be altered by some tools under Windows)
+                            str(Path(sys.executable.lower()).parents[0])
+                            != base_dir.lower()
                             and
                             # for 'binary+pip' installations (within a virtual env)
                             # python is inside 'base_dir'/Scripts
-                            str(Path(sys.executable).parents[1]) != base_dir
+                            # (warning : the case of the path in sys.executable
+                            # can be altered by some tools under Windows)
+                            str(Path(sys.executable.lower()).parents[1])
+                            != base_dir.lower()
                         )
                         # Under Linux or MacOS a bin/ folder exists
                         or str(Path(sys.executable).parents[1]) != base_dir