➜

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 serhiy.storchaka
Recipients frankmillman, ghaering, petri.lehtinen, pitrou, python-dev, serhiy.storchaka, thiderman
Date 2013-02-24.08:22:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361694164.59.0.684684903911.issue14720@psf.upfronthosting.co.za>
In-reply-to
Content 
convert_timestamp() can silently return wrong result if seconds saved with more than millisecond precision (i.e. '2012-04-04 15:06:00.000123456'). I propose or truncate fractional part to 6 digits ('{:0<6.6}') or explicitly raise an exception if len(timepart_full[1]) > 6.
History
Date User Action Args
2013-02-24 08:22:44serhiy.storchakasetrecipients: + serhiy.storchaka, ghaering, pitrou, frankmillman, python-dev, petri.lehtinen, thiderman
2013-02-24 08:22:44serhiy.storchakasetmessageid: <1361694164.59.0.684684903911.issue14720@psf.upfronthosting.co.za>
2013-02-24 08:22:44serhiy.storchakalinkissue14720 messages
2013-02-24 08:22:44serhiy.storchakacreate