time to spawn.

resources (FD/zombie) when killed at the wrong time.

#12266: Fix str.capitalize() to correctly uppercase/lowercase titlecased and cased non-letter characters.

normalization is different between unicode builds, so use a new non-BMP char and add normalization test

This fixes the use of Unicode identifiers outside the BMP in narrow builds.

Changes to crlf originally by Victor Stinner for 3.3, copied to lfcr by
me.  Manually tested.

The line about the test suite will still get printed for changes in
Tools for example, which aren’t covered by the test suite, but it’s not
a big deal IMO.

Fix closes Issue10087 -  fixing the output of calendar display in the html format. Patch by Chris Lambacher. Test Contributed by catherine.

That pipes.quote thinks all non-ASCII characters need to be quoted may
be a bug, but right now I’m committing this test to make sure I haven’t
introduced a behavior change in 3.3 when I simplified the code to use a
regex (in 5966eeb0457d).

Confirm that the prime example is actually correct.  We get so many complaints about a "buggy example" on docs@python, let us hope this cuts them in half at least.

This started out as an easy task, just add a section describing this
alternate scheme, but I found a lot of cleanup to do along the way:

- fixed inverted reST targets
- fixed entries for modules (hi abiflags!) or data files
- avoided duplicating the same options listing five or six times
- added missing entries for C headers locations
- added documentation for --install-lib
- fixed a few misuses of the option role (see #9312), but not all (not
  worth the time, but will do it in packaging docs)
- fixed some markup

The paths fixes were done with an eye on the source code in the install
command, so they really describe what’s actually done.  The situation on
Mac OS X is rather messy: the fix for #8084 touched site and sysconfig,
but distutils doesn’t use these files.  I suspect we have a mismatched
stdlib at the moment, and the fix is not even clear (see the bug report
for further discussion).

Fix closes issue12698 - make the no_proxy environment variable handling a bit lenient (accomodate spaces in between the items)