starting the test suite proper.  If _socket fails to build, that will
make this test fail with an ImportError -- handled by the test harness
as "no such module _socket" -- instead of an AttributeError deep in
CGIHTTPServer.

David Bolen.

the object being inserted was not being DECREFed.

This closes SF bug #444486.

by Albert Hofkamp.  Some editing has been done for style and markup
consistency.

This also supplies an example of importing modules and calling a function
defined in the module, so this closes SF bug #440037 as well.

(The long example code was moved to a separate file so that it would
format properly.)

This closes the SF bug (feature request) #439710.

and programmatically extend the database in different ways.

This closes the SF bug (feature request) #439710.

This should stop the bizarre translations Jack was getting from Mac CVS.

names of the test methods were not changed from the Zope-standard "check"
names to the Python-standard "test_" names, so the tests were not actually
being run.

Added test of hexadecimal character references as a regression check for
SF bug #445196.

Fix handling of hexadecimal character references (legal in XHTML) so that
they are properly interpreted as character references.
This fixes SF bug #445196.

+ Ditto pydoc.
  (IMO, both should have been done long ago -- simply didn't occur to
   me before)
+ Build the summary text into a vrbl instead of a temp file.  Doh!  Less
  fiddling, and should avoid another class of Win2K permission problems.
Bug:  the "auto vertical scrollbar" control on the summary page doesn't
work (never creates a scrollbar, no matter how much text).  So forced a
vertical scrollbar there.

markup inconsistencies.

old-style CoreFoundation.h.

  the --with-suffix=.exe, but it seems that that is also true for cygwin
  (or not? should I automatically set it?)
- Got --with-next-framework to build on OSX. This is only the build bit,
  the install still has to be done manually. Moreover, the Python build order
  isn't really suited to frameworks (where you want to do 'build lib',
  'install lib and framework', 'link executable against installed framework'
  in that order).

Removed: it doesn't work anymore, and it wasn't all that useful anyway. The FrameWork testcode shows similar functionality.

Added an optional (and ignored) 3d parameter to open() to make the signature compatible with posixmodule.
Added the various O_ constants (by stealing the code from posixmodule).

test_fileinput now passes.

Removed duplicate definnitions of PyObject_AS_GC and PyObject_FROM_GC (occurred only if GC was off).

summary of the preceding choices.  No idea if this is "the right way" to
do it, but it's exactly painful enough to make me suspect it's the only
way <wink>.