fix(windows): running tests in a virtual environment (alt 2) #2216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Description
On windows, starting with python 3.7,
virtual environments use a venvlauncher startup process This does not play well when counting spawned processes or when relying on the pid of the spawned process to do some checks e.g. connection check per pid
This commit detects this situation and uses the base python executable to spawn processes when required.
2nd alternative to #2209, exposes PYTHON_EXE_ENV to be set as the base environment when starting a process using PYTHON_EXE.
The 1st commit always uses
env= PYTHON_EXE_ENV
.The 2nd commit removes occurrences when calling
psutil.tests.spawn_testproc
(either directly or indirectly) which uses this as its default environment.