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 skip.montanaro
Recipients brett.cannon, eric.smith, skip.montanaro
Date 2007-09-13.12:59:37
SpamBayes Score 0.0009156638
Marked as misclassified No
Message-id <>
In-reply-to <>
Brett> Are you going to add support to strptime as well?

I looked at strptime for about two seconds then moved on.  I presume you
would know how to add it easily though. ;-)

    Brett> As for the 'time' module, I don't think it would be useful as it serves
    Brett> no purpose since the time tuple can't resolve to that
    Brett> resolution. 

Resolution isn't the issue.  You just make sure you add enough zeroes to
make it be microseconds.  The bigger problem is that time.strftime() takes a
tuple of ints which basically represents a struct tm.  That struct has an
int seconds field and no sub-second field.  You'd either have to start
allowing floating point tm_sec fields then either truncating or rounding
(but which?) to get ints when you need to actually generate an actual struct

Date User Action Args
2007-09-13 12:59:38skip.montanarosetspambayes_score: 0.000915664 -> 0.0009156638
recipients: + skip.montanaro, brett.cannon, eric.smith
2007-09-13 12:59:38skip.montanarolinkissue1158 messages
2007-09-13 12:59:37skip.montanarocreate