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)

  (closes SF bug #621057)
- add missing whitespace around assignment operator

everytime a LOAD_CONSTANT is encountered, created, or overwritten.

Added two tests to cover cases affected by the patch.

  reliably on WinME with FAT32.
* Native speaker rewrite of the comment block.
* Removed unnecessary backslashes from the multi-line function defintions.

Add function names to various PyArg_ParseTuple calls in bz2module.c.

nothing in gc currently cares, the original coding could screw up if,
e.g., you tried to move a node to the list it's already in, and the node
was already the last in its list.

No longer assumes that the input is NOP free.

in some platforms.

containing these functions.  (I will backport to Python 2.3)

raise a ValueError for dangling delimiters (the delimiter itself is returned).

Introduced gc_list_move(), which captures the common gc_list_remove() +
gc_list_append() sequence.  In fact, no uses of gc_list_append() remained
(they were all in a gc_list_move() sequence), so commented that one out.

gc_list_merge():  assert that `from` != `to`; that was an implicit
precondition, now verified in a debug build.

Others:  added comments about their purpose.