dmypy: fix test failure on py39 #8793
Merged
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
There's a fun Python 3.9 only test case failure, where "Daemon started" is output after the error message from parsing options. I ended up needing to bisect to figure out why this consistently breaks on Python 3.9. The issue is caused by python/cpython#17646 (which fixes a surprisingly old BPO).
Collaborator
Author
|
cc @gvanrossum |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There's a fun Python 3.9 only test case failure, where "Daemon started" is
output after the error message from parsing options. I ended up needing to
bisect to figure out why this consistently breaks on Python 3.9. The issue is
caused by python/cpython#17646 (which fixes a
surprisingly old BPO).