[issue10654] test_datetime fails on Python3.2 windows binary

Max added the comment: This is still occurring with the release version of Python 3.2, installed from the 32-bit MSI, on Windows XP. -- nosy: +max-alleged ___ Python tracker __

[issue10654] test_datetime fails on Python3.2 windows binary

Alexander Belopolsky added the comment: > + "NotImplemented" was printed Hmm, looks like a compiler bug to me. Can anyone reproduce this on a debug build? In any case, someone with a Windows setup will have to troubleshoot this further. Note that the code in abstract.c is supposed to conve

[issue10654] test_datetime fails on Python3.2 windows binary

Hirokazu Yamamoto added the comment: Sorry, - "NotImplementedError" was printed + "NotImplemented" was printed -- ___ Python tracker ___ ___

[issue10654] test_datetime fails on Python3.2 windows binary

Hirokazu Yamamoto added the comment: "NotImplementedError" was printed. This happened when subclass of date or subclass of datetime. (plain classes and subclass of time didn't print this) // Code from _datetime import date, datetime class SubclassDate(date

[issue10654] test_datetime fails on Python3.2 windows binary

Alexander Belopolsky added the comment: On Wed, Dec 8, 2010 at 2:21 PM, Hirokazu Yamamoto wrote: .. > / > > from datetime import datetime > > class SubclassDatetime(datetime): >    sub_var = 1 > > a = SubclassDatetime(2002, 3, 2, 17, 6) > # Add/sub in

[issue10654] test_datetime fails on Python3.2 windows binary

Hirokazu Yamamoto added the comment: By changing from datetime import datetime to from _datetime import datetime I can see same behavior. -- ___ Python tracker ___ _

[issue10654] test_datetime fails on Python3.2 windows binary

Hirokazu Yamamoto added the comment: This is shortest code to reproduce. But strange, I can see TypeError on VC6(both Debug and Release) E:\>e:\python-dev\py3k\pc\VC6\python.exe x.py Traceback (most recent call last): File "x.py", line 10, in a+i TypeError: unsupported operand type(s) fo

[issue10654] test_datetime fails on Python3.2 windows binary

Hirokazu Yamamoto added the comment: == FAIL: test_computations (test.datetimetester.TestSubclassDateTime_Fast) -- Traceback (most recent call last): File "c:

[issue10654] test_datetime fails on Python3.2 windows binary

Alexander Belopolsky added the comment: Hirokazu, Please rerun the test with a -v flag like this: C:\Python32>.\python -m test.regrtest -v test_datetime This should tell us whether the failure comes from C (Fast) implementation or Python (Pure) one. The test in question simply tests that da

[issue10654] test_datetime fails on Python3.2 windows binary

Changes by R. David Murray : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10654] test_datetime fails on Python3.2 windows binary

Brian Curtin added the comment: I don't see this on a US/English version of Windows 7 with 3.2b1 installed. -- nosy: +brian.curtin ___ Python tracker ___ ___

[issue10654] test_datetime fails on Python3.2 windows binary

New submission from Hirokazu Yamamoto : I'm not sure why this happens, I can see this on official python3.2 beta1 windows binary. C:\Python32>.\python -m test.regrtest test_datetime [1/1] test_datetime test test_datetime failed -- Traceback (most recent call last): File "c:\Python32\lib\test\d