This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author larry
Recipients gvanrossum, larry, loewis, r.david.murray
Date 2012-02-26.15:56:44
SpamBayes Score 0.00285027
Marked as misclassified No
Message-id <>
I suggest that publishing nanoseconds as a plain int would be a nasty API.  Consider what it would do to os.utime:

    if isinstance(mtime, int):
        # must be st_mtime_ns, it's in nanoseconds, use as-is
        value = mtime
        assert isinstance(mtime, float)
        # must be st_mtime, it's in seconds, multiply by a billion
        value = mtime * 1000000000

Have we ever published an API that treated a parameter as two wildly different numbers based solely on whether the parameter was an int or a float?
Date User Action Args
2012-02-26 15:56:45larrysetrecipients: + larry, gvanrossum, loewis, r.david.murray
2012-02-26 15:56:45larrysetmessageid: <>
2012-02-26 15:56:44larrylinkissue14127 messages
2012-02-26 15:56:44larrycreate