The 3 failures are:  test_compile test_hexoct test_sys.
------------------
test_compile failed -- eval('0xffffffff') gave
4294967295, but expected -1

 - Should this case be special cased for 32 vs 64 bit
archs?
------------------
test_hexoct fails in the unsigned tests:

test_hex_unsigned (test.test_hexoct.TextHexOct) ... FAIL
test_oct_unsigned (test.test_hexoct.TextHexOct) ... FAIL

AssertionError: 2147483648 != -2147483648L
------------------
test_sys is specifically in _getframe(sys.maxint):
        int depth = -1;

        if (!PyArg_ParseTuple(args, "|i:_getframe",
&depth))
                return NULL;
This raises an OverflowError instead of a ValueError
which is expected.
Should all "i"s in sysmodule be changed to "l"s with
corresponding changes to long for the C variable?  Or
is the test bogus and we should use a value smaller
than maxint?

Logged In: YES 
user_id=6380

Thanks for checking!

test_compile.py, eval('0xffffffff'): yes, on a 64-bit
machine this should test eval('0xffffffffffffffff') and
expect -1.

Ditto for test_hex/oct_unsigned (use 0x800000000000 etc.)

test_sys: since I don't expect anyone to ever have 2 billion
frames, change the test -- using an explicit 2000000000
would be fine IMO, as would be an explicit 0x7ffffff.

Logged In: YES 
user_id=33168

Checked in as:
 Lib/test/test_compile.py 1.17
 Lib/test/test_sys.py 1.3
(still need to fix test_hexoct)

Logged In: YES 
user_id=33168

Checked in as:
 Lib/test/test_hexoct.py 1.3

That's all for now.