1. Acknowledge the welknown difference that jython
allows continue in the finally clause.

2. Avoid using _testcapi when running with jython.

This closes patch "[ #490417 ] Jython and test_exceptions"

looking worse and worse if you deactivate/activate the window
a few times. I don't know how to fix this properly, but I'm beginning
to think that it's almost impossible to support the Appearance
manager properly due to the way W works. Time for W2?...

pickled and we do *not* expect exceptions from either pickle or
cPickle.

information automatically.

with Python 2.2.

Should this be labeled as changed?  How?)

ignored and that mode was ignored before Python 2.2.
This closes SF bug #490098.

especially since the documentation described it in detail.
This partially closes SF bug #490098.

conversation with Robin Dunn in SF patch #490402.

includes files that do not exist, explain the intended use of the interface,
and show how to ensure an expected file really exists.
This closes SF bug #490399.

Don't even try to import _socket when running under Jython.

twice!  Fixed this by avoiding the import of test_email, which loads
the module a second time in that situation, and fiddled the __main__
section to resemble other test suites using unittest.

Anthony Roach.
Release the global interpreter lock around platform spawn calls.
Bugfix candidate?  Hard to say; I favor "yes, bugfix".
These clearly *should* have been releasing the GIL all along, if for no
other reason than compatibility with the similar os.system().  But it's
possible some program out there is (a) multithreaded, (b) calling a spawn
function with P_WAIT, and (c) relying on the spawn call to block all their
threads until the spawned program completes.  I think it's very unlikely
anyone is doing that on purpose, but someone may be doing so by accident.

casts with a variable oself that has the proper type.  A smart
compiler may put this thing into a register.

(I'm not sure what good this does except satisfy my desire to
understand this function; I got a report about an uninitialized read
from Insure++ about this function and it hurt my eyes to even look at
it.  I gotta run away or I'll get tempted to reformat the entire
file...)

out the for loop at the end intended to zero out new items wasn't
doing anything, because sv->ob_size was already equal to newsize.  The
fix slightly refactors the function, introducing a variable oldsize
and doing away with sizediff (which was used only once), and using
oldsize and newsize consistently.  I also added comments explaining
what the two for loops do.  (Looking at the CVS annotation of this
function, it's no miracle a bug crept in -- this has been patched by
many different folks! :-)

This closes patch "[ #490330 ] String format bug in test_b2."

detector.
This closes SF bug #484950.

so that test_sundry won't fail if the bsddb module is absent.

Not being able to copy PythonCore to the system-folder is not a fatal error, on OSX the user may not have permission to do so. Also  give a more informative message in this case.

Fixes bug 475253.

    [ #417634 ] configuring without C++ compiler name

by checking that we're not about to try to compile C++ files with "yes".

Now we wait for the system where the C++ compiler *is* called yes...

Bug fix candidate for 2.1 branch.

(I imagine the other recent leak patches are bug fix candidates, too,
but I forgot to mark mine as such.)

Bump version number

(At least for the repeatable test case that Tim produced.)

pattern_subx(): Add missing DECREF(filter) in both exit branches
(normal and error return).  Also fix a DECREF(args) that should
certainly be a DECREF(match) -- because it's inside if (!args) and
right after allocation of match.

annoying that often you have to hit ^C numerous times before it
works.  The solution: before the "except:" clause, insert "except
KeyboardInterrupt: raise".  This propagates KeyboardInterrupt out,
stopping the test in its tracks.

obnoxious to compute and easier to explain.  No compromise on safety.

I was squashing spurious overflows in the implementation, I got hung up
on this point).

distutils for the library modules built as shared objects.  A better solution
appears possible, but with the threat that the distutils becomes more
magical ("complex").
This closes SF bug #458343.

still fail on importing modules that link with libraries that fail
their initialization code (such as windowing libraries when we don't have
access to the window server) and that is what I really wanted to fix.

as OSX HFS+) and if so add an extension to the python executable, but
only in the build directory, not on the installed python.

   adjust it when a versioned interpreter is supplied (#!.../python2 ...)

Had nothing to do with rich comparisons -- some stack cleanup code was
lost as a result of merging in Neil Schemenauer's generators patch.
Reinserted the stack cleanup code, skipping it when yielding.