Mark Keller added the comment:
+1 to what Steve said
--
___
Python tracker
<https://bugs.python.org/issue42041>
___
___
Python-bugs-list mailing list
Unsub
Mark Keller added the comment:
Paul explained precisely of what I was going through when I reached out to you
with this:
> then the "running executable" is "path/to/venv/scripts/python.exe", and so
> the path containing the running executable is "path/t
Mark Keller added the comment:
This sounds good to me Paul, thank you again!
--
___
Python tracker
<https://bugs.python.org/issue42041>
___
___
Python-bug
Mark Keller 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
New submission from Mark Keller :
Hey,
Wanted to report this weird behavior I saw recently. Let me first explain how
to reproduce and then talk about where I think the issue comes from.
I attached a tar.gz file with 2 Python files in it.
Here's how to reproduce:
0. Make sure that pytest
