Skip to content

honour ensure_ascii for unquoted identifier keys - #124

Merged
dpranke merged 1 commit into
dpranke:mainfrom
iefa-m:ensure-ascii-keys
Oct 14, 2026
Merged

dpranke merged 1 commit into
dpranke:mainfrom
iefa-m:ensure-ascii-keys

Conversation

@iefa-m

@iefa-m iefa-m commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

dumps with ensure_ascii set (the default) is meant to produce ASCII-only output, matching the json module. String values are escaped correctly, but _encode_str returns identifier keys verbatim, so a non-ascii key such as café is written raw as {café: 1} and the output is no longer ASCII. Today the only way to get such a key escaped is quote_keys=True, which is an unrelated option.

Escape the non-ascii characters of an unquoted identifier key when ensure_ascii is set, the same way string values are already escaped. The parser accepts \u escapes inside identifiers, so the key stays unquoted and still round-trips through loads. Keeping the check in _encode_str means the identifier fast path and the quoted path now agree on ensure_ascii.

@dpranke
dpranke merged commit 39d98ce into dpranke:main Oct 14, 2026
8 checks passed
@dpranke

dpranke commented Oct 14, 2026

Copy link
Copy Markdown
Owner

Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants