with the fact that getgroups(2) might return
more that MAX_GROUPS on OSX.

See the issue (and python-dev archives) for the
gory details. Summarized: OSX behaves rather oddly
and Apple says this is intentional.

"roughly" done.

Closes issue 9339. Thanks Brian Brazil for the patch.

Patch by Virgil Dupras.

when calling platform.mac_ver after calling os.fork by
reading from a system configuration file instead of
using OSX APIs.

avoid failing when the framework is not
yet installed.

itself and not by others.

Closes issue 9255.

the Crash Reporter on OSX test_subprocess will trigger
the reporter.

This patch prints a warning when the Crash Reporter will
get triggered intentionally, which should avoid confusing
people.

in distutils.sysconfig matches that in the
toplevel sysconfig module.

Without this patch universal builds on OSX are
broken.

Als add a test that checks that the two version
of get_config_vars agree on important values.

#9189 for some GCC flags.

reverted distutils its 3.1 state. All new work is now happening in disutils2, and distutils is now feature-frozen.

module which is the largest module in the stdlib.

of the script being traced.  Patch by Eli Bendersky.

with EOFError.
(this is only an added test, but 2.x will get a fix too)

Remove outdated mention of deprecated functions in the string module - they have been removed in 3.x.

Bendersky for the patch.

is wrong when PY_LDFLAGS is not empty.

The bug was caused by LDSHARED getting expanded *before* sysconfig
renamed PY_LDSHARED (and simular values) to names without a PY_
prefix.

The patch tries to maintain the intended behaviour of allowing users
to set LDFLAGS in the environment and have that affect the build.

Without this patch a universal build on OSX cannot build universal
(fat binary) extensions.

the parameters.  (This is jjlee's issue3704.patch ported to py3k)

and executable specified.

with the expansion of LDSHARED when accessing that value
through sysconfig.

The problem is probably caused by the 9189.

A fix will follow shortly.

signed/unsigned chars or on integers directly derived from those. In all
cases, it could be replaced by a simple cast to (unsigned char). Reasons
for the change:

  a) Make the comment more explicit.

  b) If char is unsigned, the cast is optimized away.

  c) If char is unsigned, gcc emits spurious "array subscript
     has type 'char'" warnings.

Add configure check for a bug with gcc soft floating-point and subnormals, to help debug issue 8265.

#9279: remove the pdb.doc file, put its contents in pdb.__doc__.  Also sync this and the pdb docs, introduce a new directive for pdb commands and a role to link to them.