[issue25155] datetime.datetime.now() raises

2015-09-18 Thread STINNER Victor
STINNER Victor added the comment: Oh wow, I didn't expect such much headaches when I worked on unifiying the code to handle timestamps in the C part of CPython... > The bug was introduced while trying to support #22117: "Rewrite pytime.h to > work on nanoseconds" in reve93eeadef0c3: >

[issue25155] datetime.datetime.now() raises

2015-09-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 4ca99a0a18e4 by Victor Stinner in branch '3.5': Issue #25155: Add _PyTime_AsTimevalTime_t() function https://hg.python.org/cpython/rev/4ca99a0a18e4 -- ___ Python tracker

[issue25155] datetime.datetime.now() raises

2015-09-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 5bfcccf229c4 by Victor Stinner in branch '3.5': Issue #25155: document the bugfix in Misc/NEWS https://hg.python.org/cpython/rev/5bfcccf229c4 -- ___ Python tracker

[issue25155] datetime.datetime.now() raises

2015-09-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 203134592edf by Victor Stinner in branch 'default': Issue #25155: Add _PyTime_AsTimevalTime_t() function https://hg.python.org/cpython/rev/203134592edf -- nosy: +python-dev ___ Python tracker

[issue25155] datetime.datetime.now() raises

2015-09-17 Thread Vitaly Murashev
New submission from Vitaly Murashev: Current time on my machine with Windows7x64 is set to year 2045 for test purposes. Since Python3.5(amd64) I have an OverflowError when I am trying to call datetime.datetime.now() It looks like a regress since there was no such error on Python3.4.3 Could

[issue25155] datetime.datetime.now() raises

2015-09-17 Thread Ethan Furman
Changes by Ethan Furman : -- nosy: +belopolsky ___ Python tracker ___ ___

[issue25155] datetime.datetime.now() raises

2015-09-17 Thread Zachary Ware
Changes by Zachary Ware : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list

[issue25155] datetime.datetime.now() raises

2015-09-17 Thread Josh Rosenberg
Josh Rosenberg added the comment: It looks like between 3.4.3 and 3.5, datetime_best_possible changed from using _PyTime_gettimeofday with a _PyTime_timeval to using _PyTime_AsTimeval with struct timeval. The difference is that _PyTime_timeval appears to have been defined with a proper time_t