[issue9070] Timestamps are rounded differently in py3k and trunk

[Alexander Belopolsky]

New submission from Alexander Belopolsky belopol...@users.sourceforge.net:

In the trunk:

 datetime.utcfromtimestamp(0.994)
datetime.datetime(1970, 1, 1, 0, 0, 1)

In py3k:

 datetime.utcfromtimestamp(0.994)
datetime.datetime(1970, 1, 1, 0, 0, 0, 99)


See issue1478429 - it appears that rounding up was intentional, but I am adding 
2.7 because py3k behavior seems to be more natural.

--
assignee: belopolsky
components: Extension Modules
messages: 108536
nosy: belopolsky, georg.brandl, mark.dickinson, tim_one
priority: normal
severity: normal
stage: unit test needed
status: open
title: Timestamps are rounded differently in py3k and trunk
type: behavior
versions: Python 2.7, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9070
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9070] Timestamps are rounded differently in py3k and trunk

[Alexander Belopolsky]

Alexander Belopolsky belopol...@users.sourceforge.net added the comment:

My mistake.  I had datetime.py from pypy in the directory from which I ran the 
trunk python.  The problem is also in the latest sandbox version of 
datetime.py, but this is not yet part of cpython proper.

Refiled as pypy bug at http://codespeak.net/issue/pypy-dev/issue548

--
resolution:  - invalid
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9070
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com