[issue24979] Allow timezone offsets greater than 24 hours

TJ added the comment: Thanks for the pointer to #5288. Happy to consolidate there. In my reading of #5094 (from which I pulled your RFC 2822 reference), the justification I found was "For the allowable range, follow the datetime docs as someone might be relying on that specification already".

[issue24979] Allow timezone offsets greater than 24 hours

Alexander Belopolsky added the comment: I always thought that restriction came from ISO 8601, but at the moment I don't have it to check. -- ___ Python tracker

[issue24979] Allow timezone offsets greater than 24 hours

Changes by Berker Peksag : -- nosy: +belopolsky ___ Python tracker ___ ___

[issue24979] Allow timezone offsets greater than 24 hours

Alexander Belopolsky added the comment: BTW, the specific issue that OP complains about is not a datetime issue: apparently pytz has an even tighter restriction on timezone offsets. I am going to close this as a third party issues, but those who support relaxing datetime.timezone restriction

[issue24979] Allow timezone offsets greater than 24 hours

Alexander Belopolsky added the comment: The timezone offset range restriction is not arbitrary. It was discussed in issue 5094 (see msg107059 and responses to it.) Nevertheless, there is an open proposal to remove all restrictions on offset values and allow it to be an arbitrary timedelta.

[issue24979] Allow timezone offsets greater than 24 hours

New submission from TJ: The datetime module only supports timezone offsets within 24 hours of UTC: https://docs.python.org/3/library/datetime.html#datetime.tzinfo.utcoffset This seems like an arbitrary restriction, and prevents the library from being used in arbitrary timezone translations.