Complete the rewrite pass; add a few more items; bump version number to 0.90; remove comment about draft status

I don't think the fix here is very good, but I'm not sure what would
be better.  In particular, we should not be defining _SGIAPI, but lots
of things break if we remove it.

PyOS_InputHook and PyOS_ReadlineFunctionPointer).

The inaccuracies were causing problems in framework builds on Mac OS X.

building a fair portion of the documentation as info.

  documented here, and according to Tim, should never have been there
- misc. cleanups for consistency

I tested against VC 7.0 and it caused no problems there.

- add a convenience target to create the package list directly

- convert tabs to spaces

    objects get made
  - improve the description of attribute retrieval from
    classes and class instances
  - add brief documentation of static method and
    class method objects.

SF patch #764594.

paper-size hook.
SF patch #772550.

module had been compiled.  It gives too many spurious warnings.

module had been compiled.  It gives too many spurious warnings.

C yet anyway.

Add reminder list of things to document; mention sys.getcheckinterval() and socket.timeout exception

the info conversion the \comment LaTeX macro mapped to a Texinfo @ignore
macro.  Unfortunately, py2texi.el is not smart enough to avoid generating
links to the @ignore'd section, which causes makeinfo to croak.

Exposing this text is probably not the most correct thing to do, as this
documentation really belongs in the C API manual.  This does get the info
files generated, however, which is a more practical goal considering the
impending release of 2.3rc1.

Prompted by a discussion on comp.lang.python.

skip over functions with private names (as indicated by the underscore
naming convention).  The old default created too much of a risk that
user tests were being skipped inadvertently.  Note, this change could
break code in the unlikely case that someone had intentionally put
failing tests in the docstrings of private functions.  The breakage
is easily fixable by specifying the old behavior when calling testmod()
or Tester().  The more likely case is that the silent failure was
unintended and that the user needed to be informed so the test could be
fixed.

these make sense even without that processing chain.

conversion to support.  Keep the content as normal content, with a
note that this applies starting in Python 2.3.

The !PyType_Check(base) check snuck in as part of rev 2.215, but was
unrelated to the SF patch that is mentioned in the checkin comment.
The test is currently unnecessary because base is set to the return
value of best_bases(), which returns a type or NULL.

by controling the font.