Technically these functions were around in some of the Python 3.4
prereleases. So add a more accurate version constraint.

To handle the Python version differences, handle the definitions of
`PyMem_Raw*` functions in `ModuleSetupCode`. Then extern them in
`cpython.mem` without using a version check or a specific header.

In Python 3.4+, Raw memory helper functions were added to wrap, track,
and check `malloc` and `free` calls for C memory outside of the GIL.
These have the same API as the existing `PyMem_*` calls except they use
Raw and never require the GIL. For Python 2/3 compatibility, export the
existing `PyMem_` functions on Python 2 as `PyMem_Raw` where they act
basically equivalently. These are especially important as Python 3.6
changed the existing `PyMem_` functions to allocate from pymalloc
instead of the C allocator meaning the GIL must now be held with them.
So these are Python 2/3 alternatives that can be relied on to not
require the GIL.

Use the print function in the nonecheck example

Enable some tests that were unintentionally not being executed because docstrings in cdef functions are not visible to Python.

Repair incorrect return value usage in test runner when checking gcc version. Fails on Windows when gcc is not available (with an error trying to regex parse None).

Make a test work in Py3.7 that changed behaviour in Python 3.7 ("generator_stop" future import became active by default).

Closes #2494.

Closes #2484.

Fix calling va_arg function with a NULL argument from generated C++ code

C++ allows NULL to be a literal 0 [1], and this actually happens on some Linux
systems when linux/stddef.h happens to be included [2]. When 0 is passed to a
variadic function as a 7th or later argument, it is passed on the stack, and
Clang encodes this on AMD64 with "mov dword ptr [rsp], 0" because it is an
int. This sets lower 32 bits to zero, but leaves upper 32 bits unchanged.
When they happen to be non zero, the called function that expects the last
argument to be a zero pointer reads past the last intended argument and
eventually segfaults.

[1] https://en.cppreference.com/w/cpp/types/NULL
[2] https://stackoverflow.com/a/31285400/1687334
[3] https://godbolt.org/g/o4Av7Q

Pythran: verify that pythran supports called Numpy APIs

Moving compilation from the reference guide to the userguide Part 3

Moving compilation from the reference guide to the userguide Part 2

Moving compilation from the reference guide to the userguide Part 1

Closes #2494.

Signed-off-by: Stefan Behnel <stefan_ml@behnel.de>

Exclude EOL-ed Py3.3 from list of supported CPython versions (since we cannot test it on travis anymore). Probably not a big deal for anyone out there, given that even LTS distributions tend to have at least 3.4.

Signed-off-by: Stefan Behnel <stefan_ml@behnel.de>