Author p-ganssle
Recipients belopolsky, joernheissler, p-ganssle, xtreak
Date 2019-07-22.14:01:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563804090.81.0.299217227223.issue37642@roundup.psfhosted.org>
In-reply-to
Content
I have been thinking about this more and I think the two issues (`min` and `max` vs. the incompatibility between C and Python) should be considered two separate issues.

My reasoning is that a change of the value of `timezone.min` and `timezone.max` is not something I'd be comfortable backporting to 3.7, because it has the potential to cause failures in some test suites (for example, `datetime.now(tz=datetime.timezone.max).isoformat()` will start returning a string that does not conform to ISO 8601, which has no support for sub-minute offsets). However, differences between the C and Python implementations are a violation of at least the spirit of PEP 399 and I think it should be backported to 3.7.
History
Date User Action Args
2019-07-22 14:01:30p-gansslesetrecipients: + p-ganssle, belopolsky, joernheissler, xtreak
2019-07-22 14:01:30p-gansslesetmessageid: <1563804090.81.0.299217227223.issue37642@roundup.psfhosted.org>
2019-07-22 14:01:30p-gansslelinkissue37642 messages
2019-07-22 14:01:30p-gansslecreate