[issue3147] tests for sys.getsizeof fail on win64

2008-06-29 Thread Robert Schuppenies
Robert Schuppenies <[EMAIL PROTECTED]> added the comment: Fixed in r64533. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3147] tests for sys.getsizeof fail on win64

2008-06-26 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > long's structure is 'lP PP l H' No, it's a VAR-sized object, and ob_size is a Py_ssize_t, which is best represented as a 'P' as you already did for other types. I suggest 'lP PP P H'. > the function size which is 'lp PP 9l' According

[issue3147] tests for sys.getsizeof fail on win64

2008-06-26 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I can't quite follow your layout of a longint; in debug mode, I think it is - 2P (next/prev) - ssize_t (refcnt) - P (type) - ssize_t (size) - digits Notice that a ssize_t is 64 bits on Win64, so there shouldn't be any longs in the structure

[issue3147] tests for sys.getsizeof fail on win64

2008-06-26 Thread Robert Schuppenies
Robert Schuppenies <[EMAIL PROTECTED]> added the comment: The tests still do not pass on the AMD64 W2k8. Surprisingly, struct.calcsize behaves as expected, but sizeof() on the C level does not. The former seems to assumes long to be 4 byte in size, the latter 8! The tests pass until it comes to

[issue3147] tests for sys.getsizeof fail on win64

2008-06-19 Thread Amaury Forgeot d'Arc
New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: the buildbot "AMD64 W2k8 trunk" systematically fails with the messages: == FAIL: test_specialtypes (test.test_sys.SizeofTest)