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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, Arfrever, belopolsky, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall, skrah, vstinner
Date 2011-09-09.23:57:29
SpamBayes Score 5.0603022e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
On Fri, Sep 9, 2011 at 5:42 PM, Larry Hastings <> wrote:
> How is this superior to using either Decimal or float128?

It is explicit about the units of time used.  If we use named tuples
and retain C API field names, stat_result.tv_atimespec.tv_sec will
clearly mean number of seconds and stat_result.tv_atimespec.tv_nsec
will clearly mean nanoseconds.  Even if we use plain tuples, the
convention will be obvious to someone familiar with C API.  And
familiarity with C API is expected from users of os module, IMO.
Those who need higher level abstractions should use higher level
Date User Action Args
2011-09-09 23:57:30Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, larry, nadeem.vawda, Arfrever, r.david.murray, skrah, rosslagerwall, khenriksson
2011-09-09 23:57:29Alexander.Belopolskylinkissue11457 messages
2011-09-09 23:57:29Alexander.Belopolskycreate