➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients acucci, belopolsky, berker.peksag, cvrebert, elixir, ezio.melotti, gvanrossum, jerry.elmore, lemburg, matrixise, r.david.murray, skip.montanaro, terry.reedy, tim.peters, vstinner
Date 2015-12-15.20:22:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450210948.41.0.784456528722.issue19475@psf.upfronthosting.co.za>
In-reply-to
Content 
> Actually, nanosecond = dt.microsecond*1000.

I was thinking in terms breaking the fractional part of say

00:00:00.123456789

into

mili = 123
micro = 456
nano = 789

but you are right, a correct analogy for dt.microsecond in this case will be nanosecond=123456789 or 123456000 until we start storing enough precision.
History
Date User Action Args
2015-12-15 20:22:28belopolskysetrecipients: + belopolsky, lemburg, gvanrossum, tim.peters, skip.montanaro, terry.reedy, vstinner, ezio.melotti, r.david.murray, cvrebert, berker.peksag, matrixise, elixir, jerry.elmore, acucci
2015-12-15 20:22:28belopolskysetmessageid: <1450210948.41.0.784456528722.issue19475@psf.upfronthosting.co.za>
2015-12-15 20:22:28belopolskylinkissue19475 messages
2015-12-15 20:22:28belopolskycreate