Conversation
With the latest release, pyRFC3339 allows a more flexible format. Prior
versions required an explicit T separator before the time section even
though the spec allows for a space.
Both of these are considered valid formats:
1970-01-01T00:00:02.500Z
1970-01-01 00:00:02.500Z
keelerm84
changed the title
jsonbailey
approved these changes
Aug 29, 2025
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.
With the latest release, pyRFC3339 allows a more flexible format. Prior
versions required an explicit T separator before the time section even
though the spec allows for a space.
While we still support the older version of pyRFC3339, we only test against the latest version, and can safely update this invalid test.
Both of these are considered valid formats: