getting Infs, NaNs, or nonsense in 2.1 and before; in yesterday's CVS we
were getting OverflowError; but these functions always make good sense
for positive arguments, no matter how large).

Repaired the ldexp docstring (said the name of the func was "ldexp_doc").

Fixed a few missing return values.

useful to people extending Python. Suggested by
Alexandre Parenteau.

__builtin__.dir().  Moved the guts from bltinmodule.c to object.c.

--enable-framework.
Some modules that are also useful outside a fullblown application are
always built.

artist (and a certain artist didn't jump in, yet).

   Slightly modified version of patch from Jon Nelson (jnelson).

   INSTALLED_FILES output.  Modified version of a patch from
   Jon Nelson (jnelson)

"/" and "//", and doesn't really care what they *mean*, just that both
are tried (and that, whatever they mean, they act similarly for int and
long arguments).

This closes SF patch #451538.

    have used the attribute argument provided as a parameter

mostly changes of / operators into //.  Once or twice I did more or
less than recommended.

way it's called each time a generator is resumed.  The tracing of normal
functions should be unaffected by this change.

This closes SF bug #458223.

Fixed a markup error which caused an em dash to be presented as a minus sign.
This closes SF bug #458350.

change their basic behavior:  When parsing something that cannot possibly
be valid in either HTML or XHTML, raise an exception.

  operators per line or statement are now on by default, and -m turns
  these warnings off.

- Change the way multiple / operators are reported; a regular
  recommendation is always emitted after the warning.

- Report ambiguous warnings (both int|long and float|complex used for
  the same operator).

- Update the doc string again to clarify all this and describe the
  possible messages more precisely.

the -Qwarnall option, so I've changed this to only filter out the one
warning that's a problem in practice.

broken declaration-like things.

regarding bare ampersands in content.

Fixed.

curses, far too old for _cursesmodule.c.

e.g., (1L << 40000)/(1L << 40001) returns 0.5, not Inf or NaN or whatever.

the fiddling is simply due to that no caller of PyLong_AsDouble ever
checked for failure (so that's fixing old bugs).  PyLong_AsDouble is much
faster for big inputs now too, but that's more of a happy consequence
than a design goal.