GitLab

Prevent Cython types in annotations from ending up plainly in the __annotations__ dict. Convert them into strings instead.

Configure another Cython option in test runner from *inside* the shard runner to support non-forking setups (i.e. Windows).

Configure Cython options in test runner from *inside* the shard runner to support non-forking setups (i.e. Windows).

Also parses variable annotations as type declarations.
Closes #1850.

Disable refnanny in PyPy since it otherwise risks to access partly initialised objects, e.g. tuples.

Disable refnanny in PyPy since it otherwise risks to access partly initialised objects, e.g. tuples.

add "--failfast" (stop on first failure) mode to test runner (if supported by Python's unittest module)

disable "initial_file_path" test in Py3.5+ since it's superseded by the ModuleSpec metadata during module initialisation

extend tests to cover some more internal signature cases of CPython builtins (METH_FASTCALL with and without keywords in P3.7)

This makes Pythran numpy backend only activated when such directive is
used. Update the documentation accordingly.

When the user asked for it (thanks to the --np-pythran flag), use
Pythran's Numpy implementation as a backend for numpy operation. This
flag forces the C++ mode, as the Pythran implementation is written in
C++. Distutils integration through the 'np_pythran' flag of the
cythonize API is also provided.

This commit also adds a Pythran mode for the tests, that can enable the
pythran mode for the C++ tests, and allows the reuse of Cython tests to
test for the Pythran integration.

see
https://mail.python.org/pipermail/cython-devel/2016-April/004776.html

Also note better support for gcc variants that are not named 'gcc' exactly.

Right now this is the only such test. There are other tests that generate code that uses long double math functions, but not in a way that appears to break the test.

This issue is particular to Cygwin since on Cygwin distutils.spawn uses os.fork(). Deleting DLLs can lead to Cygwin's fork() breaking, due to trying to load a DLL that no longer exists.  This means that the test run will use a little more disk space on Cygwin, but still allows full (or partial) cleanup at the end.

make test runner exit with non-0 return status on exceptions (this shadowed an actual bug in this branch)