[issue40218] sys.executable is a false path if python is executed from gdb

Volker Weißmann added the comment: Ok, thank you. I hope that the gdb guys will respon -- ___ Python tracker ___ ___ Python-bugs-lis

[issue40218] sys.executable is a false path if python is executed from gdb

Change by Terry J. Reedy : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue40218] sys.executable is a false path if python is executed from gdb

Ammar Askar added the comment: The reason you're seeing gdb still work even when all Pythons are deleted is because it embeds a Python interpreter in itself (https://docs.python.org/3/extending/embedding.html). This issue is thus out of scope here and belongs on the gdb tracker, but I can t

[issue40218] sys.executable is a false path if python is executed from gdb

Volker Weißmann added the comment: "I have never used gdb, but I am curious what *is* the path to the python running the python code after 'python'? Is it part of or included with gdb?" I honestly don't know. I think the python interpreter gets compiled into the python binary, because as a tes

[issue40218] sys.executable is a false path if python is executed from gdb

Terry J. Reedy added the comment: I shortened the title so that 'gdb' shows. I have never used gdb, but I am curious what *is* the path to the python running the python code after 'python'? Is it part of or included with gdb? If so, this seems a gdb bug, as it is the responsibility of the