[issue44413] OverflowError: mktime argument out of range after 2019

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 producti

[issue44413] OverflowError: mktime argument out of range after 2019

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 -- ___ Python

[issue44413] OverflowError: mktime argument out of range after 2019

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 ___ ___

[issue44413] OverflowError: mktime argument out of range after 2019

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's mktime occ

[issue44413] OverflowError: mktime argument out of range after 2019

Christian Heimes added the comment: time.mktime() is a thin wrapper around the libc function mktime(3). I can confirm that glibc's mktime() on Debian 11 with glibc 2.31 is failing and returning error code -1. Fedora 35 with glibc 2.34, Alpine with musl libc 1.2.2, and RHEL 8 with glibc 2.28

[issue44413] OverflowError: mktime argument out of range after 2019

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 expect to h

[issue44413] OverflowError: mktime argument out of range after 2019

Terry J. Reedy added the comment: Thank you both. Status: Failures on Open Suse TW (Vyacheslav) and Ubuntu 20-04 (Daniel McDonald, Github Actions, and Azure Pipelines). Success on Windows (me), macOS (Catalina-me and 11.6.1-DM), Centos 7.9 and Ubuntu 18-04 (both DM) I verified that the sam

[issue44413] OverflowError: mktime argument out of range after 2019

Change by Andrei Kulakov : -- resolution: works for me -> stage: resolved -> needs patch status: closed -> open versions: +Python 3.10, Python 3.11 -Python 3.7, Python 3.8 ___ Python tracker

[issue44413] OverflowError: mktime argument out of range after 2019

Andrei Kulakov added the comment: Confirmed on Ubuntu buildbot: https://github.com/python/cpython/runs/4537544103?check_suite_focus=true -- ___ Python tracker ___ ___

[issue44413] OverflowError: mktime argument out of range after 2019

Change by Andrei Kulakov : -- pull_requests: +28343 pull_request: https://github.com/python/cpython/pull/30124 ___ Python tracker ___ __

[issue44413] OverflowError: mktime argument out of range after 2019

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. We ha

[issue44413] OverflowError: mktime argument out of range after 2019

Change by Irit Katriel : -- resolution: -> works for me stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue44413] OverflowError: mktime argument out of range after 2019

Change by Andrei Kulakov : -- nosy: +kj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue44413] OverflowError: mktime argument out of range after 2019

Andrei Kulakov added the comment: Cannot reproduce with 3.8.6 on MacOS. The code runs without any errors. As OP hasn't responded in 4 months I think we should close as "works for me". -- nosy: +andrei.avk ___ Python tracker

[issue44413] OverflowError: mktime argument out of range after 2019

Terry J. Reedy added the comment: The posted code is incomplete, improperly indented, and a bit jumbled with respect to prompts. If the bug is real, it should be possible to reproduce without pytz. I do not have it on either Windows or macOS. Vyacheslav, can you post a better failing exam

[issue44413] OverflowError: mktime argument out of range after 2019

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue44413] OverflowError: mktime argument out of range after 2019

Terry J. Reedy added the comment: An exception is not a 'crash', as defined for this tracker. 3.8 only gets security fixes. A 3.9 or 3.10 test is needed and Windows does not have pytz. -- nosy: +belopolsky, lemburg, p-ganssle, terry.reedy type: crash -> behavior ___

[issue44413] OverflowError: mktime argument out of range after 2019

New submission from Vyacheslav : date_str = "2019-06-06 10:02:00" datetime_obj = datetime.strptime(date_str, "%Y-%m-%d %H:%M:%S") datetime_obj_utc1 = datetime_obj.replace(tzinfo=pytz.timezone("America/New_York")) datetime_obj_utc2 = pytz.timezone("America/New_York").localize(datetim