Message 137593 - Python tracker

➜

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	belopolsky
Recipients	Arfrever, belopolsky, jcea, khenriksson, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall
Date	2011年06月03日.21:50:00
SpamBayes Score	0.0002825822
Marked as misclassified	No
Message-id	<BANLkTiky8Hf03gVEuFy-v-cAg0K92sPVTQ@mail.gmail.com>
In-reply-to	<1307131071.91.0.794356823268.issue11457@psf.upfronthosting.co.za>

Content
On Fri, Jun 3, 2011 at 3:57 PM, Martin v. Löwis <report@bugs.python.org> wrote: .. > I suggest that rather than using composite time stamps, decimal.Decimal is used to represent high-precision time in Python. I support this idea in theory, but as long as decimal is implemented in Python, os module should probably expose a low level (tuple-based?) interface and a higher level module would provide Decimal-based high-precision time. BTW, what is the status of cdecimal?

Content

On Fri, Jun 3, 2011 at 3:57 PM, Martin v. Löwis <report@bugs.python.org> wrote:
..
> I suggest that rather than using composite time stamps, decimal.Decimal is used to represent high-precision time in Python.
I support this idea in theory, but as long as decimal is implemented
in Python, os module should probably expose a low level (tuple-based?)
interface and a higher level module would provide Decimal-based
high-precision time.
BTW, what is the status of cdecimal?

History
Date	User	Action	Args
2011年06月03日 21:50:01	belopolsky	set	recipients: + belopolsky, loewis, jcea, mark.dickinson, lars.gustaebel, nadeem.vawda, Arfrever, r.david.murray, rosslagerwall, khenriksson
2011年06月03日 21:50:00	belopolsky	link	issue11457 messages
2011年06月03日 21:50:00	belopolsky	create

homepage