fix default value of ensure_ascii to match comments #2538
Merged
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.
Type of changes
Checklist
Description
Make the behaviour of
ensure_ascii
parameter match the comments and the documents.The default value of
ensure_ascii
is supposed to be False, but it is True in the master branch, according to the comments or the documents, like:rich/rich/__init__.py
Line 84 in bfea226
and
rich/rich/__init__.py
Line 98 in bfea226
I am not sure of the original preference, but I think the escaping result may be confusing since it looks like an additional unexpected process.
Thus I change the default value to False.