accidentally derives from TestSuite instead of TestCase.

memset() wrote one past the end of the buffer, which was likely to be unused padding or a yet-to-be-initialized local variable.  This routine is already tested by test_socket.

stderr. close() can fail if the user is out-of-quota, for example.
Fixes #959379.

TimedRotatingFileHandler class. Thanks Jeroen Vloothuis!

There is no test for this change, because there is no way to provoke memory errors on demand.  Test suite passes, though.

the debugger enter inside pdb.set_trace.

Patch #1061767: make pdb.set_trace enter enter at the stack frame
calling pdb.set_trace().

Doc patch submitted by Ilya Sandler.

the 'if' statement that performed the test.  Not all platforms run the test and
on those tests configure outputted a rogue 'no' line.

the core on OS X (also specifically mention removal of
PyMac_GetAppletScriptFile() ).

Harmless.

-- but not end -- with whitespace.

I will backport to Python 2.3.

says boundaries may begin -- but not end -- with whitespace.

I will backport to Python 2.3.

(Contributed by Bob Ippolito.)

This patch trims down the Python core on Darwin by making it
independent of CoreFoundation and CoreServices. It does this by:

Changed linker flags in configure/configure.in
Removed the unused PyMac_GetAppletScriptFile
Moved the implementation of PyMac_StrError to the MacOS module
Moved the implementation of PyMac_GetFullPathname to the
Carbon.File module

- clean up some of the generated markup

(closes SF bug #948517)

- add a command-line option to control the image type

Bugfix candidate (the vagaries aren't new <wink>), but I don't intend to
backport this.

* explanation for example with lists of lists made confusing use of
  the word "contains" to mean "is built out of".

* wrong formula for slices with step.  Is it ok to use LaTeX formulas
  (which become images in the html document)?  This version needs one
  because it's based on a fraction.  Just writing "\code{(j-i)/k}" here would
  be ambiguous because it looks like a rounding-down-to-the-previous-integer
  division, which is not what we need here.  Of course we could write
  "\code{float(j-i)/k}" but it just looks confusing.

avoiding use of popen.

(closes SF patch #1054715; backporting to release23-maint branch)

Fixes #1049003.

(SF bug #829073)

(SF bug #829073)

(SF bug #798652)