[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

Shlomo Anglister added the comment: This issue is in review stage for a long time. What's holding it? On Wed, May 9, 2018 at 8:24 AM, Shlomo Anglister wrote: > > Shlomo Anglister added the comment: > > Thanks @serhiy.storchaka and @corona10 ! > I read it, documented the relation and failed t

[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

Shlomo Anglister added the comment: Thanks @serhiy.storchaka and @corona10 ! I read it, documented the relation and failed to see the duplication. -- ___ Python tracker ___ ___

[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

Serhiy Storchaka added the comment: I think this issue is not just related to issue23607, but a duplicate of it. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Inconsistency in datetime.utcfromtimestamp(Decimal) _

[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

Dong-hee Na added the comment: Looks like this issue is related with bpo-23607. Since a decimal object is failed on PyFloat_Check(obj) of _PyTime_ObjectToDenominator, This regression bug is happened due to no chance to get float value from a Decimal object. https://bugs.python.org/issue23607

[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

Shlomo Anglister added the comment: The test code demonstrates that fromutctimestamp(1523510588.436252000) != fromutctimestamp(Decimal(1523510588.436252000)) This is related to issues: 22627 and 23607 but not a duplicate -- ___ Python tracker

[issue33296] datetime.datetime.utcfromtimestamp call decimal causes precision loss

New submission from Shlomo Anglister : Output for python2.7.11 2018-04-12-05:23:08.436252 2018-04-12-05:23:08.436252 Output for python3.4 and python3.6 2018-04-12-05:23:08.436252 2018-04-12-05:23:08.00 -- components: Library (Lib) files: timestamp_decimal_test.py messages: 315385