[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

2020-10-25 Thread Eryk Sun
Change by Eryk Sun : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

2020-10-25 Thread Ronald Oussoren
Ronald Oussoren added the comment: Can this issue be closed? Fixing #36439 would also fix this issue. -- ___ Python tracker ___

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

2019-11-01 Thread Paul Ganssle
Paul Ganssle added the comment: Changing the superceder here as I think #36439 matches better than #37527. -- nosy: +p-ganssle resolution: duplicate -> status: closed -> open superseder: Timestamp conversion on windows fails with timestamps close to EPOCH -> Inconsistencies with

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

2019-09-20 Thread Ammar Askar
Ammar Askar added the comment: Thanks for the report Alexandre, this has to do with issues with negative numbers in Window's time APIs. There's already a bug open for this, so I've marked it as a duplicate. -- nosy: +ammar2 resolution: -> duplicate stage: -> resolved status: open

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

2019-09-20 Thread Alexandre Ouellet
New submission from Alexandre Ouellet : in a python console on a windows machine: import datetime d = datetime.datetime.fromtimestamp(0) d >datetime.datetime(1969, 12, 31, 19, 0) d.timestamp() >OSError: [Errno 22] Invalid argument on a macOS machine : d = datetime.datetime.fromtimestamp(-1)