Conversation
+0530 was read as +05:00 because the minute slice assumed a colon.
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
1 participant
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.
2003-12-31T10:14:55+0530came back as 05:14:55 UTC. The same instant written+05:30is 04:44:55 UTC. The minute slice starts after a colon, so a four-digit offset kept the hours and dropped the tens digit of the minutes.A four-digit offset is now hours then minutes.
+05:30,-08:00, andZare unchanged.-0530was 15:14:55 UTC and is now 15:44:55 UTC.pytest tests/test_date_parsers.py(76 passed). An Atom entry with<updated>2003-12-31T10:14:55+0530</updated>now parses to 04:44:55 UTC, matching+05:30.