Daniel McDonald added the comment:
Sounds good, thank you, Terry
--
type: enhancement -> behavior
___
Python tracker
<https://bugs.python.org/issu
Daniel McDonald added the comment:
A definitive assessment was obtained by Aurelien with Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001774
In brief, the OverflowError is expected and correct.
Two factors contribute to the difference in observed behavior. First, the
Daniel McDonald added the comment:
For reference, the bug reports with Debian and Ubuntu are at the following URLs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001774
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1954963
Daniel McDonald added the comment:
Thank you, Christian, I apologize for missing your reply. That is great advice,
and I will do so.
--
___
Python tracker
<https://bugs.python.org/issue44
Daniel McDonald added the comment:
The use of tm_isdst=1 appears to trigger the overflow, and occurs when varying
other aspects of the timetuple.
Python's mktime wrapper can throw OverflowError in two places. The thrown error
is the second location, following the call to glibc
Daniel McDonald added the comment:
Thank you, Terry. I'm currently exploring modifications to the test Andrei made
within a fork of CPython using Github Actions (ubuntu-latest). These
modifications include debug prints in the CPython mktime call, and some
parameter exploration. I expe
Daniel McDonald added the comment:
I'd like to politely request this issue be reopened.
We recently observed a similar, if not the same, OverflowError during
continuous integration using Github Actions on ubuntu-latest (20.04). We can
produce the error using pure Python without pytz
