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.

of PY_FORMAT_SIZE_T to "l" for Mac OSX.  I don't know a better define
to use.  This should get rid of the warnings on other platforms and Mac too.

These tests should be improved.  Hopefully this fixes variations when
flipping back and forth between fpdef and fplist.

Backport candidate.

In addition to testing positive numbers, verify negative numbers work in configure.
In order to avoid compiler warnings on OS X 10.4, also change the order of the check
for the format character to use (PY_FORMAT_SIZE_T) in the sprintf format
for Py_ssize_t.  This patch changes PY_FORMAT_SIZE_T from "" to "l" if it wasn't
defined at configure time.  Need to verify the buildbot results.

Backport candidate (if everyone thinks this patch can't be improved).

  which breaks negative counts
* added test for negative numbers
will backport to 2.5.1