Message75313
Ruby recently added support of millisecond and nanosecond to strftime.
This is their changeset:
http://redmine.ruby-lang.org/repositories/revision/ruby-19?rev=18731
To use the extended strftime, one can do:
>> Time.now.strftime('%Y-%m-%dT%H:%M:%S.%L%z')
.. "2008-10-29T17:46:03.895+0800"
In the current implementation of Python, both datetime and time modules
have strftime. Like in Ruby, the strftime in datetime module is a
method. But the strftime in time module is a function, which takes time
value to be formatted from argument, and which must be a 9-tuple
returned by gmtime or localtime. No microsecond data in the tuple,
unfortunately.
I think as the first step we can make datetime.datetime.strftime do
microsecond. I prefer microsecond to milli- or micro- second because it
is something from the the system.
The current Ruby implementation use %L or %3N for millisecond, %6N for
microsecond, and %N or %9N for nanosecond. I am not sure where they came
from. Hope there can be some widely accepted standard. |
|
Date |
User |
Action |
Args |
2008-10-29 09:53:56 | wangchun | set | recipients:
+ wangchun, christian.heimes, baloan |
2008-10-29 09:53:56 | wangchun | set | messageid: <1225274036.26.0.151382551479.issue1982@psf.upfronthosting.co.za> |
2008-10-29 09:53:55 | wangchun | link | issue1982 messages |
2008-10-29 09:53:53 | wangchun | create | |
|