Repository navigation
Compatibility fixes for simplejson v4 - #928
Merged
Merged
Conversation
JanWeldert
approved these changes
Apr 24, 2026
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
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.
Resolves #927.
Locally passed all tests with simplejson v3.18.0 (neither allow_nan nor array_hook), v3.20.2 (no array_hook), and v4.0.1 (both allow_nan and array_hook). Python version used throughout: 3.14.4.
Details:
NumpyDecoderdepending on the detected version of simplejson, now just initialise the base class with different sets of argumentsarray_hookinitialisation argument ofNumpyDecoder(doesn't make sense IMO)json_array_numpy()now has a newarray_hook=Noneparameter and ignores any possible attempt of setting it by emitting a warning