Skip to content

bpo-31800: Support for colon when parsing time offsets #4015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abalkin merged 13 commits into from
Oct 26, 2017
Merged

bpo-31800: Support for colon when parsing time offsets #4015

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
567666a
Support for colon when parsing time offsets
mariocj89 Oct 16, 2017
0facd08
Add news entry
mariocj89 Oct 17, 2017
af68297
Docs for parsing using %z and colons
mariocj89 Oct 17, 2017
e0e3873
Add support for Z on %z directive
mariocj89 Oct 19, 2017
7c53307
Update docs to reflect the addition of parsing Z
mariocj89 Oct 21, 2017
d184e7b
Add support for parsing seconds
mariocj89 Oct 23, 2017
3809303
Add support for microsecond on strptime
mariocj89 Oct 23, 2017
7548704
Add test case with the new format on datetimetester
mariocj89 Oct 23, 2017
69e655c
Improve error message on : invalid use
mariocj89 Oct 23, 2017
f718b37
Typo: utc -> UTC
mariocj89 Oct 23, 2017
5cfeeee
Handle gmtoff miliseconds via a separate variable
mariocj89 Oct 24, 2017
546b7b8
Enrich NEWS entry with latest changes
mariocj89 Oct 25, 2017
c20b57f
Update docs on new %z behaviour
mariocj89 Oct 25, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs to reflect the addition of parsing Z
  • Loading branch information
@mariocj89
mariocj89 committed Oct 23, 2017
commit 7c533072cfbaea789cc8e6bda29287c8c9bae99e
7 changes: 4 additions & 3 deletions Doc/library/datetime.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2175,9 +2175,10 @@ Notes:
The UTC offset is not restricted to a whole number of minutes.

.. versionchanged:: 3.7
When ``%z`` directive is provided to the :meth:`strptime` method, offsets
with colons will be parsed as well. For example, offsets like ``'+01:00'``
will be parsed as an offset of one hour.
When ``%z`` directive is provided to the :meth:`strptime` method, any valid
RFC-822/ISO 8601 standard utftime-offset can be parsed. For example, strings

@abalkin abalkin Oct 25, 2017

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utftime-offset? This should be UTC offset, right?

like ``'+01:00'`` will be parsed as an offset of one hour and or ``'Z'`` will
be transofmred to a 0 utc offset.

``%Z``
If :meth:`tzname` returns ``None``, ``%Z`` is replaced by an empty
Expand Down
2 changes: 1 addition & 1 deletion Misc/NEWS.d/next/Library/2017-10-17-20-08-19.bpo-31800.foOSCi.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
Add support for parsing utc offsets with colon when using %z in strptime
Add support for parsing RFC-822/ISO 8601 utf offsets