comparisons that could lead to infinite recursion.

The buildbots will tell us which platform does support or not negative years.

 * With Visual Studio, year have to be in [1; 9999]
 * Add more tests on the year field

Victor Stinner for pointing this out.

This applies only when generating strings from non-RFC compliant binary
input; it makes the existing recoding behavior more consistent (ie:
now no data is lost when recoding).

Before this patch if a value being encoded had an embedded newline,
the line following the newline would have no leading whitespace,
and the whitespace it did have was encoded into the word.  Now
the existing whitespace gets turned into a blank, the way it does
in other header reformatting, and the _continuation_ws gets added
at the beginning of the encoded line.

Revert r87821 which moved the source link to the wrong section (from the module intro covering the module to a section on thread imports).

non-Python managed memory while it is being modified by another thread.
Patch by Matt Bandy.

function will now format any year when time.accept2dyear is false and
will accept years >= 1000 otherwise.  The year range accepted by
time.mktime and time.strftime is still system dependent, but
time.mktime will now accept full range supported by the OS. Conversion
of 2-digit years to 4-digit is deprecated.

On Windows, set the binary mode on stdin, stdout, stderr and all
io.FileIO objects (to not translate newlines, \r\n <=> \n). The Python parser
translates newlines (\r\n => \n).

see #10181.

on an existing file.

(this does not seem to be easily testable)

the application.  Initial patch by Clovis Fabricio.

timestamp profiling (--with-tsc): the preprocessor test for the PowerPC
support now looks for "__powerpc__" as well as "__ppc__": the latter seems to
only be present on OS X; the former is the correct one for Linux with GCC.