Closed
Conversation
Better json serialization/deserialization
Member
Author
|
No downside, but I'm using flask/jinja2 and I just use the same encoder/decoder here. One thing we could do, is specify the serialization method, and the encoder/decoders that go with it. So, something like: which would open the door to something like using yaml, or pickle. I can add this if you like this weekend. |
565044a to
11e4d54
Compare
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.
Allows for custom serialization/deserialization and defaults to the built json encoder/decoder. This also sets the encoder/decoder for all places
json.dump(s)andjson.load(s)is used (i.e.gen_unique_id).This allows you to use a custom encoder/decoder and still use
unique=Trueon tasks.TODO: add tests, and docs