Author martin.panter
Recipients belopolsky, gvanrossum, martin.panter, shanmbic
Date 2015-10-05.00:39:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444005541.81.0.315681068579.issue24954@psf.upfronthosting.co.za>
In-reply-to
Content
I added some comments on Rietveld. I guess the documentation should get notices and What’s New entries saying it is new in 3.6. Test cases would be good, including negative ones to check error handling is sensible if the Z is missing. Also shanmbic, perhaps look at signing the contributor agreement <https://www.python.org/psf/contrib/> if you haven’t already.

Adding to the list of format codes means that the statement at the top of the list about them all being required by C89 will need fixing.

For parsing, perhaps the existing %z code could be extended to accept colons, without needing to specify a new %:z code. Although if %:z is added for formatting, it should also be supported for parsing.

I am not convinced that it is worth adding %::z or %:::z to Python. The documentation of tzinfo.utcoffset() says it returns the offset “in minutes”, hinting that sub-minute offsets are not supported. RFC 3339 acknowledges that sub-minute offsets exist in history, but AFAIK neither RFC 3339 nor ISO 8601 support them. So I think it is too specialized to build %::z into Python. And I don’t imagine the %:::z necessary precision version would be used much either.
History
Date User Action Args
2015-10-05 00:39:01martin.pantersetrecipients: + martin.panter, gvanrossum, belopolsky, shanmbic
2015-10-05 00:39:01martin.pantersetmessageid: <1444005541.81.0.315681068579.issue24954@psf.upfronthosting.co.za>
2015-10-05 00:39:01martin.panterlinkissue24954 messages
2015-10-05 00:39:00martin.pantercreate