'Run python file' doesn't work in Git Bash

[ingempo]

When clic on upper rigth button (Run python file):

DEVOPS-WIP-01+opalrtlinux@DEVOPS-WIP-01 MINGW64 /c/work/hardware-qualification (OS-1494_add_hs_api_support) $ /work/hardware-qualification/.venv/Scripts/python.exe /work/hardware-qualification/test_hypersim.py bash: /work/hardware-qualification/.venv/Scripts/python.exe: No such file or directory

My interpreter is /.venv/Scripts/python.exe

[ingempo]

if i change to Command prompt, it works.

[NIV27e]

I attempted to replicate the issue of 'Run python file' not working in Git Bash on my macOS setup but was unsuccessful. Here's a brief overview of what I did:

Setup: I set up a Python environment and ran a simple script through VSCode using the macOS Terminal.
Outcome: The script executed successfully without any errors.

It seems that the issue might be specific to Git Bash on Windows, possibly due to differences in how path resolutions are handled between operating systems. I recommend further testing on Windows or investigating how Git Bash handles paths compared to other shells.

Observations:

1. Path Syntax and Handling: Path syntax differs significantly between Windows and Unix-like systems. While Unix uses forward slashes (/) for paths, Windows typically uses backslashes (). Git Bash attempts to bridge this gap by translating Unix paths to Windows paths, which can sometimes lead to inconsistencies or incorrect paths.

2. Executable Files and Environment Variables: Standards also vary, with Windows executables typically ending in .exe and using %VAR% format for environment variables, as opposed to the Unix $VAR format and permission-based executability.

Possible Causes:
The issue might stem from how Git Bash handles these translations and emulates Unix paths and commands within the Windows environment. This could lead to scripts generating paths that don't actually resolve correctly under Windows file system rules.

Suggestions for Resolution:

1. Path Handling: Ensure that any scripts or tools explicitly handle different path conventions depending on the operating system. This might involve checking the operating system at runtime and adjusting paths accordingly.

2. Cross-Platform Testing: More rigorous testing across different environments could help identify these issues earlier. Testing in both native Unix environments and Windows with Git Bash can highlight discrepancies that need addressing.

3. Use Cross-Platform Libraries: For development, consider using libraries that abstract away these differences, such as Python’s os.path or pathlib modules, which handle file system paths intelligently across platforms.

I hope this helps clarify the potential root causes and provides a path forward for resolving the issue. I’m looking forward to any further insights or suggestions on this matter!

[anthonykim1]

Hello @ingempo Thanks for filing the issue.
Please note that git bash isn't officially supported by Python extension at the moment. Reference: #22908

@NIV27e Appreciate the thorough comments on this and this would definitely come in handy once we get time, bandwidth in the future to be ready to support Git bash!