Uh oh!
There was an error while loading. Please reload this page.
Make importexport black-safe... - #1449
Merged
Merged
Conversation
We do this by removing the fragile unicode characters (which kind of isn't Python safe either), and test export *outside* of the doctest hidden mechanism which was wrong (if expedient) also.
so "\t" isn't misinterpreted
rockyforce-pushed
the
black-importexport
branch
2 times, most recently
from
June 25, 2021 03:37
b4648db to
8b1925dCompare
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We do this by removing the fragile unicode characters (which
kind of isn't Python safe either), and test export outside
of the doctest hidden mechanism which was wrong (if expedient) also.