By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,306 Members | 1,621 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,306 IT Pros & Developers. It's quick & easy.

Getting milliseconds in Python

P: n/a
I am trying to record how long an operation takes, but can't seem to
find a function that will allow me to record the timestamp in
milliseconds, maybe I am looking in the wrong place?

Jul 18 '05 #1
Share this Question
Share on Google+
15 Replies


P: n/a
mjs7231 wrote:
I am trying to record how long an operation takes, but can't seem to
find a function that will allow me to record the timestamp in
milliseconds, maybe I am looking in the wrong place?


I have no idea where you look - but the time-module has IMHO a descriptive
enough name - so look there and be a happy camper.

--
Regards,

Diez B. Roggisch
Jul 18 '05 #2

P: n/a
"Return the time as a floating point number expressed in seconds since
the epoch, in UTC. Note that even though the time is always returned as
a floating point number, not all systems provide time with a better
precision than 1 second. While this function normally returns
non-decreasing values, it can return a lower value than a previous call
if the system clock has been set back between the two calls. "

This is no good, I am looking for milliseconds, not seconds.. as stated
above.

Jul 18 '05 #3

P: n/a
>>>>> "mjs7231" == mjs7231 <mj*****@gmail.com> writes:

mjs7231> This is no good, I am looking for milliseconds, not
mjs7231> seconds.. as stated above.

Well seconds/1000.0 = millseconds -- or are you worries about floating
point error?

7 >>> from datetime import datetime
8 >>> dt = datetime.now()
9 >>> dt.microsecond
Out[9]: 20222

Converting to milliseconds is left as an exercise for the reader...

See also the timeit module...
JDH
Jul 18 '05 #4

P: n/a
mjs7231 wrote:
"Return the time as a floating point number expressed in seconds since
the epoch, in UTC. Note that even though the time is always returned as
a floating point number, not all systems provide time with a better
precision than 1 second. While this function normally returns
non-decreasing values, it can return a lower value than a previous call
if the system clock has been set back between the two calls. "

This is no good, I am looking for milliseconds, not seconds.. as stated
above.


If your system _can_ provide better accuracy than seconds, it is returned as
fraction of a second. That is the whole point the result of time being a
float and not an int.

--
Regards,

Diez B. Roggisch
Jul 18 '05 #5

P: n/a
"This is no good, I am looking for milliseconds, not seconds.. as
stated
above. "

The docs are not very clear. I had the same issue when I was trying to
do the same thing, but the time and datetime modules return
milliseconds on my linux machines.

Jul 18 '05 #6

P: n/a
"mjs7231" <mj*****@gmail.com> wrote:
"Return the time as a floating point number expressed in seconds since
the epoch, in UTC. Note that even though the time is always returned as
a floating point number, not all systems provide time with a better
precision than 1 second. While this function normally returns
non-decreasing values, it can return a lower value than a previous call
if the system clock has been set back between the two calls. "

This is no good, I am looking for milliseconds, not seconds.. as stated
above.


are you sure you know what a millisecond is?

can you spot the milliseconds here:
import time
time.time() 1108575508.234 time.time() 1108575515.062

or here:
time.clock() 1.6349019714375455 time.clock() 2.2402415685960024 time.clock()

2.7715522631434739

</F>

Jul 18 '05 #7

P: n/a
mjs7231 wrote:
This is no good, I am looking for milliseconds, not seconds.. as stated
above.


That IS what you want.

seconds * 100 = milliseconds

--
Brian Beck
Adventurer of the First Order
Jul 18 '05 #8

P: n/a
Brian Beck wrote:
That IS what you want.

seconds * 100 = milliseconds


are you sure you know what a millisecond is?

(duck)

Jul 18 '05 #9

P: n/a
Brian Beck wrote:
That IS what you want.

seconds * 100 = milliseconds


May I assume that this IS what you want ?

()___
()//__/)_________________()
||(___)//#/_/#/_/#/_/#()/||
||----|#| |#|_|#|_|#|_|| ||
||____|_|#|_|#|_|#|_|#||/||
|| |#|_|#|_|#|_|#|_||

:)

(credits to jgs, found on http://www.ascii-art.de/ascii/ab/bed.txt)

--
Amand Tihon
Jul 18 '05 #10

P: n/a
Fredrik Lundh wrote:
Brian Beck wrote:

That IS what you want.

seconds * 100 = milliseconds

are you sure you know what a millisecond is?

(duck)


Touché.

But it was a typo.

--
Brian Beck
Adventurer of the First Order
Jul 18 '05 #11

P: n/a
On 2005-02-16, Brian Beck <ex****@gmail.com> wrote:

seconds * 100 = milliseconds

are you sure you know what a millisecond is?

(duck)


Touché.

But it was a typo.


Oh, you meant 'seconds / 100 = milliseconds'?

(canard)
Jul 18 '05 #12

P: n/a
Curt wrote:
Oh, you meant 'seconds / 100 = milliseconds'?

(canard)


I assume you're suggesting that there are two typos in my original post
(the * and the 100)...

Despite a millisecond being a thousandth of a second, given the number
of seconds provided by the time module, he does have to *multiply* by a
thousand to get the number of milliseconds.

2 seconds * 1000 = 2000 milliseconds

So, aside from the 100 in the original post, it may look misleading, but
that is what he would need to do...

--
Brian Beck
Adventurer of the First Order
Jul 18 '05 #13

P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> "Brian" == Brian Beck <ex****@gmail.com> writes:

Brian> Despite a millisecond being a thousandth of a second [...]

A math teacher! A math teacher! My kingdom for a math teacher!

Martin

- --
Homepage: http://www.cs.auc.dk/~factotum/
GPG public key: http://www.cs.auc.dk/~factotum/gpgkey.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using Mailcrypt+GnuPG <http://www.gnupg.org>

iEYEARECAAYFAkIUxPkACgkQYu1fMmOQldXH3QCdGcw3grK/R17kfakMBhxU1Io/
4ukAoJl+gysL9q/6j1G8LYPZz7NawEV+
=1CNL
-----END PGP SIGNATURE-----
Jul 18 '05 #14

P: n/a
Martin Christensen wrote:
A math teacher! A math teacher! My kingdom for a math teacher!

Martin


Man, this is the hottest topic on c.l.py since that Lazaridis guy...

--
Brian Beck
Adventurer of the First Order
Jul 18 '05 #15

P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> "Brian" == Brian Beck <ex****@gmail.com> writes:

Brian> Man, this is the hottest topic on c.l.py since that Lazaridis
Brian> guy...

.... which was really the point of my joke, even if it did belly flop
somewhat. This whole discussions brought to mind a cartoon where a
group of doctors were performing open heart surgery. One of them says,
"Okay, how many of us believe that the heart has _four_ chambers?,"
and a few of the others raise their hands. I intended it as a 'let's
call in the professors to determine if 2+2=4', but, well... :-)

Martin

- --
Homepage: http://www.cs.auc.dk/~factotum/
GPG public key: http://www.cs.auc.dk/~factotum/gpgkey.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using Mailcrypt+GnuPG <http://www.gnupg.org>

iEYEARECAAYFAkIUyzAACgkQYu1fMmOQldWVdACdHLxtUi4TtF Cl0ZW6wf65Hu9M
ioMAoMWAHrkS5lhQw5V0cJXVO1nk76MO
=6MXl
-----END PGP SIGNATURE-----
Jul 18 '05 #16

This discussion thread is closed

Replies have been disabled for this discussion.