function parameter.

parameter to a function. When function arguments are marked as const,
this means that the function should not modify them, not that
non-const arguments are not allowed.
This also fixes a test that began failing because this change resulted
in a slightly different error message when conversion to a const
qualified argument is not possible.

__Pyx_PyInt_TrueDivideObjC: switch comparison order

FROM_PY_FUNCTION: Cast to sdigit after unary minus, not before

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 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.

[Build/Dependencies] added a comparision for setuptools.Extension class

This is done with the T=* syntax, similar to default args
of cdef methods.

This does, however, expose us to types that we can't
explicitly declare.

Optimize dependency checking

Ensure that extension's include_dirs is a list

This change allows to pass generator (e.g. itertools.chain) as
include_dirs if for some reason evaluation of include directories needs
to be delayed e.g. due to simultaneous dependency on cython and numpy.

Fix parse_list("")

Use correct macros to check GCC version

use slightly faster PyObject_Malloc() instead of PyMem_Malloc() for small memory allocation needs (<= 512 bytes)

Cpp iterator declarations.

Don’t crash when a C class isn’t defined in the pxd

Fix typo in numpy tutorial

Hide some parts of stack trace in __PYX_ERR macro

These were already failing when this was added to the build matrix.

Enable tests on python 3.5-dev

Enable tests on python 3.5-dev to catch problems with upcoming python releases early.

Set up c_code_config options properly when autogenerating header files.