Message 236552 - Python tracker

➜

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.

In-reply-to
Author	tbarbugli
Recipients	tbarbugli
Date	2015年02月24日.22:38:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1424817522.64.0.693607620573.issue23517@psf.upfronthosting.co.za>

Content
Hi, I am porting a library from python 2.7 to 3.4 and I noticed that the behaviour of datetime.utcfromtimestamp is not consistent between the two versions. For example on python 2.7.5 datetime.utcfromtimestamp(1424817268.274) returns a datetime with 274000 microseconds the same code in python 3.4 returns a datetime with 273999 microseconds.

Content

Hi,
I am porting a library from python 2.7 to 3.4 and I noticed that the behaviour of datetime.utcfromtimestamp is not consistent between the two versions.
For example on python 2.7.5
datetime.utcfromtimestamp(1424817268.274)
returns a datetime with 274000 microseconds
the same code in python 3.4 returns a datetime with 273999 microseconds.

History
Date	User	Action	Args
2015年02月24日 22:38:42	tbarbugli	set	recipients: + tbarbugli
2015年02月24日 22:38:42	tbarbugli	set	messageid: <1424817522.64.0.693607620573.issue23517@psf.upfronthosting.co.za>
2015年02月24日 22:38:42	tbarbugli	link	issue23517 messages
2015年02月24日 22:38:42	tbarbugli	create

homepage