datetime does not support timestamps after 2038 on 32-bit

[bmwiedemann]

Bug report

cpython on 32-bit platforms cannot handle dates beyond 2038-01-19

python3.10 -c 'import datetime; datetime.datetime.fromtimestamp(3000000000)'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
OverflowError: timestamp out of range for platform time_t

Your environment

• CPython versions tested on: 3.8, 3.9, 3.10
• Operating system and architecture: openSUSE-Tumbleweed 20230110 i586

This comes from
https://github.com/python/cpython/blob/8e9d08b0/Modules/_datetimemodule.c#L4982
https://github.com/python/cpython/blob/8e9d08b0/Python/pytime.c#L173

These could use __time64_t if available or we compile everything with __TIMESIZE=64

[sobolevn]

It works on my machine (macOS 10.14) on main:

(.venv) ~/Desktop/cpython  main ✔                                                    
» ./python.exe -c 'import datetime; datetime.datetime.fromtimestamp(3000000000)' 

(.venv) ~/Desktop/cpython  main ✔                                                    
» echo $?                                                                        
0

The same for 3.9:

Python 3.9.15 (main, Nov 22 2022, 17:18:20) 
[Clang 11.0.0 (clang-1100.0.33.16)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime; datetime.datetime.fromtimestamp(3000000000)
datetime.datetime(2065, 1, 24, 8, 20)

I don't say that this is not a bug, I say that this is totally system-specific.

[mcepl]

It works on my machine (macOS 10.14) on main:

Is your system 32bit? I doubt it with Mac.

[sobolevn]

No, it is 64 bit

[mcepl]

No, it is 64 bit

Then your comment is unfortunately irrelevant.

[sobolevn]

@mcepl yeap, that's what I said :)

I don't say that this is not a bug, I say that this is totally system-specific.

[bmwiedemann]

I guess, this could be solved outside of python by rebuilding our 32-bit Linuxes with
-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64

So that their (or glibc's) time_t would have 8 bytes.