Konrad was too kind.  Not only did it raise an exception, the specific
exception it raised made no sense.  These are old bugs in complex_pow()
and friends:

1. Raising 0 to a negative power isn't a range error, it's a domain
   error, so changed c_pow() to set errno to EDOM in that case instead
   of ERANGE.

2. Changed complex_pow() to:

A. Used the Py_ADJUST_ERANGE2 macro to try to clear errno of a spurious
   ERANGE error due to underflow in the libm pow() called by c_pow().

B. Produced different exceptions depending on the errno value:
   i) For errno==EDOM, raise ZeroDivisionError instead of ValueError.
      This is for consistency with the non-complex cases 0.0**-2 and
      0**-2 and 0L**-2.
   ii) For errno==ERANGE, raise OverflowError.

Bugfix candidate.

   * 'macdef' (macro definition) wasn't parsed correctly
   * account value not reset for a subsequent 'default' line
   * typo: 'whitepace' -> 'whitespace'

Bugfix candidate.

Bugfix candidate.

Remove unused no_compile flag
Initialize the Boolean attribute .compile to 0 instead of None

Bugfix candidate.

    got this right?

Bugfix candidate, unless Thomas notes a problem.

   (Someone should check the other commands for this same error.)

Bugfix candidate.

possibly converting from AppleSingle.

in MachoPython. As we don't have MacOS.HandleEvent() we drop these on
the floor (with a print).

we have GUSI's void sync().

This patch makes it possible to pass Warning instances as the first
argument to warnings.warn. In this case the category argument
will be ignored. The message text used will be str(warninginstance).

is "ignore". Fixes #529104.

Add iterator support to pulldom.DOMEventStream

New feature, so not a bugfix candidate (though it should be safe for inclusion)

Can go into 2.2.x, but not necessary.

Bugfix candidate?  Don't know -- never bothered me, but it's minor
either way.

Windows some modules are considered (by me, and I don't care what anyone
else thinks about this <wink>) to be part of "the core" despite that they
happen to be compiled into separate DLLs (the "to DLL or not to DLL?"
question on Windows is nearly arbitrary).  Making the pymalloc entry
points available to them allows the Windows build to complete without
incident when WITH_PYMALLOC is #define'd.

Note that this isn't unprecedented.  Other "private API" functions we
export include _PySequence_IterSearch, _PyEval_SliceIndex, _PyCodec_Lookup,
_Py_ZeroStruct, _Py_TrueStruct, _PyLong_New and _PyModule_Clear.

    last Medusa release)

Should be safe as a bugfix candidate, though it's not fixing a bug.

              prototypes remain.  Noted by Yakov Markovitch.

Bugfix candidate.

for (reported by Keith Briggs).
Wrap some very long lines.

This was stated before, but a minor grammatical error made it difficult to be
sure of the meaning.
This closes SF bug #530143.

FakeSocket class.  Without it, the sendall() call got the method on
the underlying socket object, and that messed up SSL.

Does httplib use other methods of sockets that FakeSocket doesn't support?
Someone should take a look...  (I'll try to give it a once-over.)

2.2.1 bugfix candidate.

   exists.

the time...)

searches.  This is added after /tmp.  Closes SF bug #505488, except
that /var/tmp comes after /tmp instead of the patch's suggestion of
putting it before /usr/tmp.

[ 530285 ] redefining SRE_CODE in Modules/sre.h

malloc() and free() don't change.

Py_BuildValue by address, not by value.

2.2.1 candidate.