Python: add datetime support + pass mypy --strict + rename JSON-related methods #14
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.
This PR introduces a few changes:
to_json
andfrom_json
on generated classes toto_json_data
andfrom_json_data
. From experience with the Ruby code generation, these names are less likely to lead to confusion. The functions work with data that conforms to the JSON data model, not JSON strings itself.str
for a JTDtimestamp
, this PR has us emit a Python3datetime.datetime
.mypy --strict
. This is tested as part of the Docker testing regime._parse_rfc339
is added as a utility.Also, this PR includes
cargo fmt
. This leads to some noisy diff across a few targets.