Add allow_nan attribute to DefaultJSONProvider - #6116
Closed
Omacrow wants to merge 1 commit into
Closed
Conversation
DefaultJSONProvider now exposes an allow_nan attribute (default True, matching the existing json.dumps default), so applications can opt into strict RFC 8259 output with app.json.allow_nan = False. Refs pallets#6114
Author
|
The failing "Development Versions" check looks unrelated to this change |
Member
|
Duplicate of #2832 |
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
2 participants
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.
DefaultJSONProvider now exposes an allow_nan attribute (default True,
matching the existing json.dumps default), so applications can opt
into strict RFC 8259 output with app.json.allow_nan = False.
fixes #6114