[ENH] Accept UTC offsets in datetimes #2001
Open
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
effigies
requested review from
erdalkaraca and
DimitriPapadopoulos
as code owners
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.
As discussed in #1968, non-UTC timezones can be useful for coordinating acquisitions across time zones. The spec currently adopts RFC3339 with the exception that nonzero UTC offsets are not permitted, and the
Zoffset is optional to allow indicating local time.For backwards compatibility, I propose allowing the offsets to remain optional, but permitting the full range of RFC3339 offsets.
Separately, the current regular expression does not express the current rule, so I will open another PR against the maintenance branch for that.