BUG: Fix(up) incorrect return in SetItemFast

Sorry, my previous fix was cursed (not running the tests), now I
saw the compiler warning, and I suppose it would be good for the
tests to run error paths.

I was going to use posix_madvise(POSIX_MADV_DONTNEED) in my tests to
make sure a memory page should be evicted from kernel cache, but found
out that this operation is hardcoded to be NOOP on Glibc/Linux systems:

https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/posix_madvise.c;h=c89fa64f0749;hb=HEAD#l25
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8889e7aa461a

On the other hand, as also verified by strace, `madvise(MADV_DONTNEED)`
is not a NOOP as it actually goes to kernel by making syscall.

Since it is not possible to use posix_madvise for what should be
POSIX_MADV_DONTNEED behaviour, let's add all raw madvise behaviour flags
as documented on http://man7.org/linux/man-pages/man2/madvise.2.html

Presumably MADV_NORMAL and other behaviours that should translate 1-1 to
POSIX ones were omitted in 59ac9991 (Add pxd for mmap & friends
from "sys/mman.h" covering POSIX/Linux/BSD) to make people use the
standardised POSIX interface. However given that it turned out to be not
possible to use posix_madvise for all standard behaviours,
system-specific madvise behaviours have to be used.

* Do not use unsafe _PyMethodDef_RawFastCallKeywords
* Simplify and optimize calls, using vectorcall on Python 3.8

Do not reset "tp_print" for builtin types in Py3 at all anymore. It was never needed there (only in Py2) and not gets in the way in Py3.8/9.

* REF: make Utils dependency-free by moving search_include_directories to Main
* BUG: prefer sys.path before Cython/Include when searching for pxd files

CPython bpo-37221 reverts that backwards incompatible
change to the PyCode_New API, replacing it with a new
PyCode_NewWithPosOnlyArgs function.

CPython bpo-37221 reverts that backwards incompatible
change to the PyCode_New API, replacing it with a new
PyCode_NewWithPosOnlyArgs function.

PyGILState_STATE was added in commit 3fd6fdce (Gilnanny + pystate.pxd)
with struct type on-purpose different from what CPython actually uses
with the idea so that PyGILState_STATE cannot be coerced into int.

However as it is, it prevents PyGILState_STATE usage:

	cdef PyGILState_STATE gstate = PyGILState_Ensure()

gives

	Variable type 'PyGILState_STATE' is incomplete

Fix it by making PyGILState_STATE a defined structure.

Closes GH-3007.

The regex to match the gdb version is not intended to be interpreted as a regular string, it is designed to be used as-is as a regex.  This lets python know that minor detail.

The regex to match the gdb version is not intended to be interpreted as a regular string, it is designed to be used as-is as a regex.  This lets python know that minor detail.

And make it more flexible in terms of API change.

And make it more flexible in terms of API change.

Current checks breaks when setting 0.10.0 as a Pythran version :-/

Add compatability with Bazel 0.26