Use @force_not_colorized in test_syntactical_future_repl#152749
Merged
StanFromIreland merged 1 commit intoJul 1, 2026
Conversation
2 tasks
StanFromIreland
approved these changes
Jul 1, 2026
StanFromIreland
changed the title
test_future@force_not_colorized in test_syntactical_future_repl
Member
|
Merged, thanks. |
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
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.
Found while working on RustPython/RustPython#8181
This is the only test that checks that the literal substring of
SyntaxError: ...is not inside the output, but when coloring is enabled the output might contain a literalmaking this test to always pass