New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
find_python.bat is not properly silenced #107814
Labels
OS-windows
triaged
The issue has been accepted as valid by a triager.
type-bug
An unexpected behavior, bug, or error
Comments
Eclips4
added
OS-windows
triaged
The issue has been accepted as valid by a triager.
labels
Aug 9, 2023
zooba
pushed a commit
that referenced
this issue
Aug 9, 2023
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Aug 9, 2023
…bat (pythonGH-107815) (cherry picked from commit 1e229e2) Co-authored-by: Max Bachmann <kontakt@maxbachmann.de>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Aug 9, 2023
…bat (pythonGH-107815) (cherry picked from commit 1e229e2) Co-authored-by: Max Bachmann <kontakt@maxbachmann.de>
Thanks! The backports should get merged sometime soon, but I'll close the issue now. |
zooba
pushed a commit
that referenced
this issue
Aug 9, 2023
Yhg1s
pushed a commit
that referenced
this issue
Aug 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
OS-windows
triaged
The issue has been accepted as valid by a triager.
type-bug
An unexpected behavior, bug, or error
Bug report
When
find_python.bat
is run without a Python interpreter present on the system it installs an interpreter via nuget. However in this case it does not properly silence output to stdout when-q
is passed. This leads to issues when the user relies on only the interpreter path to be printed, which is the case when it is used inside visual studio.Linked PRs
find_python.bat
#107815The text was updated successfully, but these errors were encountered: