add 'if (PyErr_Occurred())' checks to various places so that NULL is
returned properly.

2.4 backport candidate.

* unified the way intobject, longobject and mystrtoul handle
  values around -sys.maxint-1.

* in general, trying to entierely avoid overflows in any computation
  involving signed ints or longs is extremely involved.  Fixed a few
  simple cases where a compiler might be too clever (but that's all
  guesswork).

* more overflow checks against bad data in marshal.c.

* 2.5 specific: fixed a number of places that were still confusing int
  and Py_ssize_t.  Some of them could potentially have caused
  "real-world" breakage.

* list.pop(x): fixing overflow issues on x was messy.  I just reverted
  to PyArg_ParseTuple("n"), which does the right thing.  (An obscure
  test was trying to give a Decimal to list.pop()... doesn't make
  sense any more IMHO)

* trying to write a few tests...

(unsigned long vs. unsigned int).

on undefined behaviour of the C compiler anymore.
Will backport to 2.5 and 2.4.

The compiler was checking that there was something on the fblock
stack, but not that there was a loop on the stack.  Fixed that and
added a test for the specific syntax error.

Bug fix candidate.

test for parts > 3 when we use .split(..., 2).

Documentation omitted the additional parameter to LogRecord.__init__ which was added in 2.5. (See SF #1569622).

stdint.h. Will backport.

Will backport.

running w/o subprocess.

check, resulting in obscure error messages.  Do the syntax check
first.  Bug 1562716, 1562719

string pointed to by its parameter.

to encodings.search_function() contains a dot.

datetime's strftime function.

but also for functions.

keep_blank_values and strict_parsing keyword arguments.

with a slash.

number of arguments, as was the case in Python 2.4.

keyword arguments any more (previously they accepted them, but didn't
use them).

GNOME browser in case it is a command with args.

Will backport to 2.5.

being raised when print_exc() was called without an exception set.
In version 2.4, this printed "None", restored that behavior.

not being recognized as a keyword after, e.g., this statement:
from __future__ import division, with_statement

hopes that more information will help debug the failing test on HPPA Ubuntu.