PEP 410
This commit is contained in:
parent
d475f0bcab
commit
16ee7d9cef
10
pep-0410.txt
10
pep-0410.txt
|
@ -97,9 +97,9 @@ int() instead.
|
|||
Backwards Compatibility
|
||||
=======================
|
||||
|
||||
The default timestamp type is unchanged, so there is no impact on backward
|
||||
compatibility nor on performances. The new timestamp type, decimal.Decimal, is
|
||||
only returned when requested explicitly.
|
||||
The default timestamp type (float) is unchanged, so there is no impact on
|
||||
backward compatibility nor on performances. The new timestamp type,
|
||||
decimal.Decimal, is only returned when requested explicitly.
|
||||
|
||||
|
||||
Objection: clocks accuracy
|
||||
|
@ -124,9 +124,9 @@ Alternatives: Timestamp types
|
|||
To support timestamps with an arbitrary or nanosecond resolution, the following
|
||||
types have been considered:
|
||||
|
||||
* decimal.Decimal
|
||||
* number of nanoseconds
|
||||
* 128-bits float
|
||||
* decimal.Decimal
|
||||
* datetime.datetime
|
||||
* datetime.timedelta
|
||||
* tuple of integers
|
||||
|
@ -254,7 +254,7 @@ Depending of the exact format of the tuple, the precision can be arbitrary or
|
|||
fixed. The precision can be choose as the loss of precision is smaller than
|
||||
an arbitrary limit like one nanosecond.
|
||||
|
||||
Different formats has been proposed:
|
||||
Different formats have been proposed:
|
||||
|
||||
* A: (numerator, denominator)
|
||||
|
||||
|
|
Loading…
Reference in New Issue