Repository navigation
gh-146440: Add an example for the json array_hook decoder parameter - #154522
Open
fedonman wants to merge 2 commits into
Open
fedonman wants to merge 2 commits into
fedonman wants to merge 2 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Documentation build overview11 files changed · ± 11 modified ± Modified |
Sorry, something went wrong.
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
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.
The array_hook parameter added to the JSON decoders in gh-146440 has version notes but no example, while the "Customizing JSON object decoding" section only shows object_hook and parse_float.
This adds two short examples there: one turning every JSON array into a tuple, and one pairing array_hook with object_pairs_hook to get a deeply immutable result, which is the use case the JSONDecoder docstring already describes. Both are marked # doctest: +SKIP, since the parameter needs Python 3.15 or later and the docs are often built with an older interpreter.
While there, it fixes a small wording slip in the array_hook parameter description ("decoded with as a Python list") and a typo ("structute") in the JSONDecoder docstring.
Documentation only, so there is no news entry.