Check this and raise an error when something else is used - before
this change ctypes would hang or crash when such a callback was
called.  This is a partial fix for #1574584.

Backported from trunk.

- Bug #1578513: Cross compilation was broken by a change to configure.
Repair so that it's back to how it was in 2.4.3.

to CRLF instead.

files in VC7.1 pythoncore.vcproj.

 (backport from rev. 52313)

 (backport from rev. 52311)

about the case of filenames.
 (backport from rev. 52309)

(bug #1556261).
 (backport from rev. 52307)

embedded in the string to convert.
 (backport from rev. 52305)

 (backport from rev. 52303)

arguments with the system default encoding just like the write()
method does, instead of converting it to a raw buffer.
 (backport from rev. 52301)

in inspect.findsource().
 (backport from rev. 52299)

 (backport from rev. 52297)

is started with that option.
 (backport from rev. 52295)

 (backport from rev. 52293)

 (backport from rev. 52251)

Bug #1572832: fix a bug in ISO-2022 codecs which may cause segfault
when encoding non-BMP unicode characters.  (Submitted by Ray Chason)

  (backport from rev. 52129)

  (backport from rev. 51439)

Backport the .sln and .vcproj files for PCBuild8 from the python trunk to the 2.5 maintainance branch.  This fixes build problems with visual studio 2005, and cleans up profile guided optimization.

- remove Sleepycat name now that they have been bought

 with this change.]

Cause a PyObject_Malloc() failure to trigger a MemoryError, and then
add 'if (PyErr_Occurred())' checks to various places so that NULL is
returned properly.

* unified the way intobject, longobject and mystrtoul handle
  values around -sys.maxint-1.

* in general, trying to entierely avoid overflows in any computation
  involving signed ints or longs is extremely involved.  Fixed a few
  simple cases where a compiler might be too clever (but that's all
  guesswork).

* more overflow checks against bad data in marshal.c.

* 2.5 specific: fixed a number of places that were still confusing int
  and Py_ssize_t.  Some of them could potentially have caused
  "real-world" breakage.

* list.pop(x): fixing overflow issues on x was messy.  I just reverted
  to PyArg_ParseTuple("n"), which does the right thing.  (An obscure
  test was trying to give a Decimal to list.pop()... doesn't make
  sense any more IMHO)

* trying to write a few tests...