Add more recent Python versions including
development branches and nightly build.
The motivation came from reading @brettcannon's article : https://snarky.ca/how-to-use-your-project-travis-to-help-test-python-itself/ . Trying to activate the newest Python versions on CI jobs is in most case a win-win situation: if everything works fine, there is nothing to worry about. If an issue is spotted, it is good to know about it to fix it on your side or to open a bug on Cython ( https://bugs.python.org/ ).
Also, if a failures is spotted, you can use the allow_failures option in your matrix build (more information about this in the link above).
Coverage remained the same at 44.513% when pulling 7bc7cab35e1736177347a6fa5958ccd7aa489237 on SylvainDe:master into 1de07de56d8032cca40c495d6143ca1b1a9e3526 on Parsely:master.
Coverage remained the same at 44.513% when pulling a0894558f4924e891bf95d0347b7be0e7a997544 on SylvainDe:master into 1de07de56d8032cca40c495d6143ca1b1a9e3526 on Parsely:master.
Add more recent Python versions including development branches and nightly build.
The motivation came from reading @brettcannon's article : https://snarky.ca/how-to-use-your-project-travis-to-help-test-python-itself/ . Trying to activate the newest Python versions on CI jobs is in most case a win-win situation: if everything works fine, there is nothing to worry about. If an issue is spotted, it is good to know about it to fix it on your side or to open a bug on Cython ( https://bugs.python.org/ ).
Also, if a failures is spotted, you can use the
allow_failures
option in your matrix build (more information about this in the link above).More information about how this PR happened on https://github.com/SylvainDe/CIthon .