Uses the fast update() method when a dictionary is available.

the tokenize module by test_tokenize.py.  The FutureWarnings only
appeared during installation, and I've figured out a way to suppress
those in a different way.

This seems the sanest thing to do.

of FutureWarnings.  Added a comment explaining the situation.

when given its own type as an argument.

sure these are the best fixes.

- Test maxint-1 against the negative octal constant -020000000000

- Comment out the tests for oct -1 and hex -1, since 037777777777 and
  0xffffffff raise FutureWarnings now and in Python 2.4 those
  constants will produce positive values, not negative values.  So the
  existing test seems to test something that won't be true in 2.4.

trailing `L's.

HTML tarball and use it to create a documentation tree readable and
searchable with Apple Help Viewer. The documentation also shows up in
Project Builder (if you add Python.framework to your project).

  in Python.app, and refer to it in Info.plist. This makes Apple Help
  Viewer recognize the Python documentation.
- Changed the externally visible name of Python.app to "Python" (was PythonW).

HTML tarball and use it to create a documentation tree readable and
searchable with Apple Help Viewer. The documentation also shows up in
Project Builder (if you add Python.framework to your project).

fully qualified imports) but somehow not checked in yet.

an error message and not just the missing name.

Closes SF Bug 599869.

simply PyErr_SetFromErrno

This closes bug 599163.

Closes SF patch #600861.

Minor markup changes.

usually isn't what we want anyway.

Someone else may want to tackle the mutating operations similarly.

cardinality 500; and the smaller the intersection, the bigger the speedup).

meanings.  I did not add new, e.g., ispropersubset() methods; we're
going nuts on those, and, e.g., there was no "friendly name" for
== either.

<, <=, etc methods too.

should never be used in tests.  Repaired dozens, but more is needed.