[issue36558] Change time.mktime() return type from float to int?

STINNER Victor added the comment: https://mail.python.org/pipermail/python-dev/2019-April/157125.html Guido van Rossum wrote: "Consistency with C should not be the issue -- consistency between the time functions is important. (...) So let's drop the idea." I close the issue. --

[issue36558] Change time.mktime() return type from float to int?

STINNER Victor added the comment: I started a thread on python-dev: https://mail.python.org/pipermail/python-dev/2019-April/157121.html -- ___ Python tracker ___

[issue36558] Change time.mktime() return type from float to int?

Paul Ganssle added the comment: I would say that the natural output of mktime is indeed an integer, but I can't say off the top of my head what "compatibility" refers to here, so per the principle of Chesterton's fence, without more research or historical context I'd say the default should

[issue36558] Change time.mktime() return type from float to int?

Change by STINNER Victor : -- keywords: +patch pull_requests: +12650 stage: -> patch review ___ Python tracker ___ ___

[issue36558] Change time.mktime() return type from float to int?

New submission from STINNER Victor : time.mktime() returns a floating point number: >>> type(time.mktime(time.localtime())) The documentation says: "It returns a floating point number, for compatibility with :func:`.time`." time.time() returns a float because it has sub-second resolution,