[issue42041] venv subprocess call to python resolves to wrong interpreter

[Mark Keller]

Mark Keller <markooo.keller at gmail.com> added the comment:

Thank you so much for the prompt responses.

I would say that this should be documented on the venv page (https://docs.python.org/3/library/venv.html) as I find the subprocess page too dense of information already, but I do agree that venv page is most likely not where developers would look first.

I'm a little embarrassed to say this, but I didn't even know that sys.executable existed.

So maybe the better way to document this would be to mention sys.executable on the subprocess page, just as a sure way find where the current interpreter lives and then go into detail why this behavior difference is on the venv page. Maybe have them linked to each other?

What do you think about this?

----------
components:  -Documentation
versions: +Python 3.7, Python 3.8 -Python 3.10, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue42041>
_______________________________________