Hi Kristján,
On Thu, May 03, 2007 at 07:38:04PM +0200, ?iga Seilnacht wrote:
> Those tests should be fixed to use test.test_support.MAX_Py_ssize_t instead
> of sys.maxint.
See also the bigmemtest() and bigaddrspacetest() decorators in test_support.
A bientot,
Armin.
__
> If that is the case, I have two suggestions:
> a) Propagate the Windows idiom of sizeof(size_t) != sizeof(long) by keeping
> some sys.maxsize for list length, indices, etc.
> b) Elevate int to 64 bits on windows too!
> B is probably a huge change. Not only change PyIntObject but probably create
Kristján Valur Jónsson wrote:
> Hello again.
> A lot of overflow tests fail in the testsuite, by expecting overflow using
> sys.maxint.
> for example this line, 196, in test_index.py:
> self.assertEqual(x[self.neg:self.pos], (-1, maxint))
Those tests should be fixed to use test.test_support.MAX_
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Thomas Heller
> Sent: Thursday, May 03, 2007 17:04
> To: python-dev@python.org
> Subject: Re: [Python-Dev] x64 and the testsuite
>
> Kristján Valur Jónsson schrieb:
&g
Kristján Valur Jónsson schrieb:
> Hello again.
> A lot of overflow tests fail in the testsuite, by expecting overflow using
> sys.maxint.
> for example this line, 196, in test_index.py:
> self.assertEqual(x[self.neg:self.pos], (-1, maxint))
On my (virtual) win64-machine, which has less than 1GB,
Hello again.
A lot of overflow tests fail in the testsuite, by expecting overflow using
sys.maxint.
for example this line, 196, in test_index.py:
self.assertEqual(x[self.neg:self.pos], (-1, maxint))
At the moment, I am disabling these tests with
if "64 bit" not in sys.version:
So, two questions
