Relaxed datetime/time parsing #539
Merged
Conversation
This file contains 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
Previously we strictly followed the RFC3339 format when parsing datetime and time objects from strings. We now support a few common ISO8601 compatible relaxations: - A `:` isn't required as part of the timezone component in both datetime and time strings (`2022-01-02T03:04:05.678+0102` and `2022-01-02T03:04:05.678+01:02` are treated the same). - A ` ` may be used instead of `T`/`t` as a separator between date and time components when parsing datetime strings. When encoding datetime/time objects we still strictly follow RFC3339. This eases integrating msgspec with other systems that don't strictly follow RFC3339.
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.
Previously we strictly followed the RFC3339 format when parsing datetime and time objects from strings. We now support a few common ISO8601 compatible relaxations:
A
:isn't required as part of the timezone component in both datetime and time strings (2022-01-02T03:04:05.678+0102and2022-01-02T03:04:05.678+01:02are treated the same).A
T/tas a separator between date and time components when parsing datetime strings (2022-01-02 03:04:05.678+01:02and2022-01-02T03:04:05.678+01:02are treated the same).When encoding datetime/time objects we still strictly follow RFC3339. This eases integrating msgspec with other systems that don't strictly follow RFC3339.
Fixes #537.