with MSVC.

The current order results in compiler warnings on 32 bit machines, e.g.

src/llfuse.c: In function '__Pyx_PyInt_TrueDivideObjC':
src/llfuse.c:43980:17: warning: left shift count >= width of type
                 if (8 * sizeof(long) <= 53 || (__Pyx_sst_abs(size) <= 52 / PyLong_SHIFT) || likely(labs(a) <= (1L << 53))) {

Switching the order so that the left shift is closer to the sizeof test
avoids the warning, presumably because it makes it easier for the
compiler to see that the left shift is only executed on 64 bit.

Thanks to Christian Neukirchen for doing most of the work!

The current cast isn't doing anything, because the unary minus implicitly
upcasts to int again, resulting in warnings about potentially value altering
conversions on 32 bit systems.

Fixes issue #877.

repair deep-copying (and pickling) of the control flow state in compiled Cython (extension type instances lost their state)

Fix a memory leak in ObjectHandling.c

do not use cythonize() but Cython.Distutils in setup.py to avoid Cython compilation when not building the extensions

clean up extension building in setup.py: clarify what's Py3.2-specific and use cythonize() instead of Cython.Distutils

* Add Python 3.5 to the build matrix
* Rework helper build script (copied from mpi4py)

guess longness suffix of negative decimal integer literals based on their type to prevent the C compiler from truncating their value range