Message143819
| 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 |
<CAP7h-xY0qyH-9npTwMJ90MiOv7n=ucHxvo4HoWV5tYbKgDmLgg@mail.gmail.com> |
| In-reply-to |
<1315604520.38.0.546764937836.issue11457@psf.upfronthosting.co.za> |
| Content |
On Fri, Sep 9, 2011 at 5:42 PM, Larry Hastings <report@bugs.python.org> 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
modules. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年09月09日 23:57:30 | Alexander.Belopolsky | set | recipients:
+ 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:29 | Alexander.Belopolsky | link | issue11457 messages |
| 2011年09月09日 23:57:29 | Alexander.Belopolsky | create |
|