regrtest doesn't check that tests doesn't write something to stdout anymore.

Don't replace sys.stdout by the original sys.stdout to be able to capture the
output for regrtest -W.

regrtest doesn't check that tests doesn't write something to stdout anymore.

Don't replace sys.stdout by the original sys.stdout to be able to capture the
output for regrtest -W.

If verbose is False, the output is empty. Fix also a typo in a variable name.

If verbose is False, the output is empty. Fix also a typo in a variable name.

all calls

 * Don't force verbose to True with option -W
 * Rename rerun_failed variable to output_on_failure

 * Don't force verbose to True with option -W
 * Rename rerun_failed variable to output_on_failure

replaced by a io.StringIO object by regrtest (which has no file descriptor).

a io.StringIO object by regrtest (which has no file descriptor).

faulthandler.enable() requires that sys.stderr has a fileno() method.

but captures the output and displays it on failure instead. regrtest -v doesn't
print the error twice anymore if there is only one error.

the output and displays it on failure instead. regrtest -v doesn't print the
error twice anymore if there is only one error.

... instead of using fork(): sig*wait*() functions behave differently (not
correctly) after a fork, especially on FreeBSD 6.

Skip also test_sigtimedwait_poll() on FreeBSD 6 because of a kernel bug.

distutils to packaging.

test_command_build_ext.

set the MACOSX_DEPLOYMENT_TARGET env variable for the interpreter process
on OS X.  This could cause failures in non-distutils subprocesses and was
unreliable since tests or user programs could modify the interpreter
environment after distutils set it.  Instead, have distutils set the
the deployment target only in the environment of each build subprocess.

Continue to use the previous algorithm for deriving the deployment target
value:
    if MACOSX_DEPLOYMENT_TARGET is not set in the interpreter's env:
        use the interpreter build configure MACOSX_DEPLOYMENT_TARGET
    elif the MACOSX_DEPLOYMENT_TARGET env value >= configure value:
        use the env MACOSX_DEPLOYMENT_TARGET
    else: # env value less than interpreter build configure value
        raise exception
This allows building extensions that can only run on newer versions of
the OS than the version python was built for, for example with a python
built for 10.3 or later and an extension that needs to be built for 10.5.

test_build_ext.

A patch from Vincent Legoll.

test_build_ext of test_distutils and test_command_build_ext of
test_packaging are no longer silently skipped when
run outside of a build directory.

test_build_ext of test_distutils is no longer silently skipped when
run outside of a build directory.

os.lchflags() are once again built on systems that support these
functions (*BSD and OS X).  Also add new stat file flags for OS X
(UF_HIDDEN and UF_COMPRESSED).  Also add additional tests for
os.chflags() and os.lchflags(). (Tests by Garrett Cooper)

os.lchflags() are once again built on systems that support these
functions (*BSD and OS X).  Also add new stat file flags for OS X
(UF_HIDDEN and UF_COMPRESSED).  Also add additional tests for
os.chflags() and os.lchflags(). (Tests by Garrett Cooper)

2.8 +  on Mac OS X.  (Patch by Ronald Oussoren)

on Mac OS X.  (Patch by Ronald Oussoren)