[Python-Dev] datetime nanosecond support (ctd?) (original) (raw)
schmeii maxischmeii at gmail.com
Thu Dec 11 22:58:28 CET 2014
- Previous message: [Python-Dev] datetime nanosecond support (ctd?)
- Next message: [Python-Dev] datetime nanosecond support (ctd?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2014-12-11 22:00 GMT+01:00 MRAB <python at mrabarnett.plus.com>:
On 2014-12-11 18:33, Skip Montanaro wrote:
there are likely to be situations where the caller assumes it generates a six-digit string. I did a little poking around. It seems like "%N" isn't used. Could the number of digits be specified? You could have "%9f" for nanoseconds, "%3f" for milliseconds, etc. The default would be 6 microseconds for backwards compatibility.
Ruby does that, but use %9N. (a plain %N consume 9 digits by default).
GNU date also use %N, but doesn't allow to specify the number of digits to consume. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141211/3b4d42a8/attachment.html>
- Previous message: [Python-Dev] datetime nanosecond support (ctd?)
- Next message: [Python-Dev] datetime nanosecond support (ctd?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]