fix: use sys.executable for pytest runner python_path - #760
Open
sentry[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses a
FileNotFoundErrorthat occurred when thelabel-analysiscommand, utilizing thePytestStandardRunner, attempted to executepytestvia a subprocess. The root cause was the hardcoded defaultpython_pathof'python'inPytestStandardRunnerConfigParams.On systems where the
pythonexecutable is not directly in the PATH (e.g., some macOS or Linux environments that primarily usepython3), the subprocess call would fail. This fix changes the defaultpython_pathtosys.executable, ensuring that thepytestsubprocess is always invoked using the same Python interpreter that is running thecodecov-clicommand. This makes the runner more robust and compatible across various environments.Fixes CLI-G9