Movatterモバイル変換

[Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review

• Previous message:[Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
• Next message:[Python-Dev] best place for an atomic file API
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On Feb 15, 2012, at 10:11 AM, Martin v. Löwis wrote:>I think improving datetime needs to go in two directions:>a) arbitrary-precision second fractions. My motivation for>   proposing/supporting Decimal was that it can support arbitrary>   precision, unlike any of the alternatives (except for using>   numerator/denominator pairs). So just adding nanosecond resolution>   to datetime is not enough: it needs to support arbitrary decimal>   fractions (it doesn't need to support non-decimal fractions, IMO).>b) distinction between universal time and local time. This distinction>   is currently blurred; there should be prominent API to determine>   whether a point-in-time is meant as universal time or local time.>   In terminology of the datetime documentation, there needs to be>   builtin support for "aware" (rather than "naive") UTC time, even>   if that's the only timezone that comes with Python.+1-Barry-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 836 bytesDesc: not availableURL: <http://mail.python.org/pipermail/python-dev/attachments/20120215/35aec033/attachment.pgp>

• Previous message:[Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
• Next message:[Python-Dev] best place for an atomic file API
• Messages sorted by:[ date ][ thread ][ subject ][ author ]