bpo-27413: json.tool: Add --no-ensure-ascii option.
#17472
Merged
Conversation
This file contains 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
methane
reviewed
Dec 5, 2019
methane
changed the title
--no-ensure-ascii option.
methane
approved these changes
Dec 5, 2019
|
Test is failing because stdout is not UTF-8 on Windows. |
wimglenn
force-pushed
the
json_tool_again
branch
from
b49d113
to
f5c95a3
Compare
methane
reviewed
Dec 6, 2019
wimglenn
force-pushed
the
json_tool_again
branch
from
f5c95a3
to
fb56a72
Compare
…on.dumps in the json.tool command-line-interface.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added ability to pass through
ensure_asciioptions to json.dumps in thejson.toolcommand-line interface.Some motivation: https://stackoverflow.com/questions/52712674/how-to-use-json-tool-from-the-shell-to-validate-and-pretty-print-language-files
https://bugs.python.org/issue27413