nvda

70d1894f - fix(build): fix Python interpreter calling failure when path contains spaces (#18210)

fix(build): fix Python interpreter calling failure when path contains spaces (#18210) Link to issue number: None Summary of the issue: On systems where the build directory contains spaces (e.g., under "My Codes"), NVDA's build process fails due to unquoted executable paths. Previously, this was addressed for m4.exe (see #18147) but Python interpreter paths used during SCons builds (such as for building user_docs) were not properly quoted, causing continued failures in similar scenarios. Description of user facing changes: None Description of developer facing changes: The build system SCons invokes the Python interpreter (e.g., @{sys.executable} in building scripts) in several build steps. When the interpreter’s path contains spaces (e.g., in "C:\Users\MyName\Documents\My Codes\nvda\.venv\Scripts\python.exe"), the command fails unless the path is wrapped in quotes. This PR wraps {sys.executable} in double quotes to ensure these paths are parsed correctly by the shell and avoids build errors in such environments.