Fix some 64-bit issues due to mismatch format characters w/actual data types

Add C API function Py_GetBuildNumber(), add it to the interactive prompt
banner (i.e. Py_GetBuildInfo()), and add it as the sys.build_number
attribute.  The build number is a string instead of an int because it may
contain a trailing 'M' if there are local modifications.

(reported by Chris Olds).  Backported from the 1.0.6 development
branch.

Supresses numerous pages of compiler warnings.

added missing API hooks

(e.g. cStringIO, ucnhash, etc)

build problem on AIX.

In C++, it's an error to pass a string literal to a char* function
without a const_cast().  Rather than require every C++ extension
module to put a cast around string literals, fix the API to state the
const-ness.

I focused on parts of the API where people usually pass literals:
PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type
slots, etc.  Predictably, there were a large set of functions that
needed to be fixed as a result of these changes.  The most pervasive
change was to make the keyword args list passed to
PyArg_ParseTupleAndKewords() to be a const char *kwlist[].

One cast was required as a result of the changes:  A type object
mallocs the memory for its tp_doc slot and later frees it.
PyTypeObject says that tp_doc is const char *; but if the type was
created by type_new(), we know it is safe to cast to char *.

meaningless numbers, but I figured out I would fix that bug anyway.

[Patch #1350573] zlib.crc32 doesn't handle 0xffffffff seed.  Add tests and bugfix.  Bug reported by John Schmidt; bugfix by Danny Yoo.

accepts strings only for unpickling reasons.  This check prevents the honest
mistake of passing a string like '2:59.0' to time() and getting an insane
object.

Need to check return result of PyInt_AsLong()

Will backport.

Close the fd in the close method and invalidated it.  Don't try
to close a second time when deallocating.

properties now.

Remove duplicate declarations from compile.h

This change implements a new bytecode compiler, based on a
transformation of the parse tree to an abstract syntax defined in
Parser/Python.asdl.

The compiler implementation is not complete, but it is in stable
enough shape to run the entire test suite excepting two disabled
tests.

from U+FFFD to U+FFFE which is considered more appropriate.  (from
MAL's comment)

Since I can't test this, I'm just adding a comment.  If we get access
to AIX boxes, we can test this and really resolve.  Anyone from IBM
want to offer help?

Backport candidate I suppose.

Also provide a warning if a directory is passed on the command line.
Add minimal command line test.

Will backport.

in latin_1, but Python incorrectly assumes it is in UTF-8 format

Will backport.

FreeBSD 5.3 and later versions which got thread-safe getaddrinfo(3).
(Reported by Maxim Sobolev)

returns in cStringIO.c.  Thanks to Andrew Bennetts.

This must be a backport candidate.

Fix segfault.  I tried to write a test, but it wouldn't crash
when running regrtest.  This really should have some sort of test.

Should definitely be backported.