I'm undecided if this should be backported to 2.5 or 2.5.1.
Armin suggested to wait (I'm of the same opinion).  Thomas W thinks
it's fine to go in 2.5.

Patch # 1543897.

Will backport to 2.5

Klocwork #325

(I'm not backporting this, but if someone wants to, feel free.)

Klocwork 286-287.

(I'm not backporting this, but if someone wants to, feel free.)

Klocwork #307

object so we don't leak op.  (Fixes an earlier patch to this code)

Klockwork #350

In one place where I'n not 1000% sure about the non-NULL, raise
a RuntimeError for safety.

This should fix the klocwork issues that Neal sent me.  If so,
it should be applied to the release25-maint branch also.

discussion).

Additionally, remove a faulty example showing PySequence_SetItem applied
to a newly created list object and add notes that this isn't a good idea.

on systems with low clock resolution.

Leave tk build directory to restore original path.
Invoke debug mk1mf.pl after running Configure.

generated for generator expressions.

'Save Copy As' and 'Print' hotkeys to 'y' and 't'.  Change the
Shell menu hotkey from 's' to 'l'.

M    Bindings.py
M    PyShell.py
M    NEWS.txt

    Clarify somewhat how parameters are passed to functions
    (especially explain what integer means).

    Correct the table - Python integers and longs can both be used.
    Further clarification to the table comparing ctypes types, Python
    types, and C types.

Reference:

    Replace integer by C ``int`` where it makes sense.

ignore data that arrives before the opening start tag

of the Python part of a callback function to C.  If it cannot be
converted, call PyErr_WriteUnraisable with the exception we got.
Before, arbitrary data has been passed to the calling C code in this
case.

(I'm not really sure the NEWS entry is understandable, but I cannot
find better words)

exception.  Remove a stray '?' character from the exception text
when the value is retrieved of such an object.

Includes tests.