[issue3556] test_raiseMemError consumes an insane amount of memory

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: After testing under Windows, fixed in r65773. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3556] test_raiseMemError consumes an insane amount of memory

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3556] test_raiseMemError consumes an insane amount of memory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Can you test with that patch? I personally can't test it for the next three weeks, sorry. ___ Python tracker <[EMAIL PROTECTED]> __

[issue3556] test_raiseMemError consumes an insane amount of memory

Facundo Batista <[EMAIL PROTECTED]> added the comment: Terry, I don't get to understand your comment. Could you please explain in more detail? Thank you! ___ Python tracker <[EMAIL PROTECTED]>

[issue3556] test_raiseMemError consumes an insane amount of memory

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: With sys.maxint gone in 3.0, test_raisexxx() is also gone in 3.0b2 -- nosy: +tjreedy ___ Python tracker <[EMAIL PROTECTED]> __

[issue3556] test_raiseMemError consumes an insane amount of memory

Facundo Batista <[EMAIL PROTECTED]> added the comment: Antoine, it works great, both in 2.6 and in 3.0 (with the obvious small modification). -- nosy: +facundobatista ___ Python tracker <[EMAIL PROTECTED]> __

[issue3556] test_raiseMemError consumes an insane amount of memory

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Can you test with that patch? -- components: +Tests keywords: +patch nosy: +pitrou type: -> resource usage Added file: http://bugs.python.org/file11125/memerror.patch ___ Python tracker <[EMAIL PR

[issue3556] test_raiseMemError consumes an insane amount of memory

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: You're right; this test would be pointless with that. However, I'm looking at test_exceptions' test_MemoryError that is failing for me because it gives a OverflowError instead of a MemoryError. ___ Pytho

[issue3556] test_raiseMemError consumes an insane amount of memory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > I wonder if it might be most effective to make a _testcapi interface to > PyErr_NoMemory. How would that work in this case? (I actually don't know what the test purpose of this test is.) ___ Python trac

[issue3556] test_raiseMemError consumes an insane amount of memory

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I wonder if it might be most effective to make a _testcapi interface to PyErr_NoMemory. -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]>

[issue3556] test_raiseMemError consumes an insane amount of memory

New submission from Martin v. Löwis <[EMAIL PROTECTED]>: It appears that test_unicode::test_raiseMemError was meant to produce a MemoryError. Unfortunately, on my machine (Linux 2.6.25, 32-bit processor, 1GiB main memory, plenty swap), allocation *succeed*, and then brings the machine to a near h