-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-133374: fix test_python_legacy_windows_stdio #134080
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
gh-133374: fix test_python_legacy_windows_stdio #134080
Conversation
See also #133375. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is closer to being ready than the other PR, IMHO. So up to the two contributors to see who gets there first :)
Should we use When a Windows developer runs a test on the console, will a new annoying console appear for a moment? (I cannot run test on Windows Desktop soon.) |
It will, but don't we have a resource for this already? If the new console doesn't appear, annoying characters get typed over the test results for some similar tests. So I'm pretty sure they're all behind a resource. |
Thanks @methane for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Thanks @methane for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, @methane, I could not cleanly backport this to
|
(cherry picked from commit 652d693) Co-authored-by: Inada Naoki <songofacandy@gmail.com>
GH-134314 is a backport of this pull request to the 3.14 branch. |
test_python_legacy_windows_stdio
intest_cmd_line
isn't actually working #133374