Add most recent Python versions in Travis CI#70
Merged
harshildarji merged 1 commit intoTheAlgorithms:masterfrom Mar 7, 2017
SylvainDe:master
Merged
Add most recent Python versions in Travis CI#70harshildarji merged 1 commit intoTheAlgorithms:masterfrom SylvainDe:master
harshildarji merged 1 commit intoTheAlgorithms:masterfrom
SylvainDe:master
Conversation
Add more recent Python versions including development branches and nightly build.
noorinrahila
added a commit
to noorinrahila/Python
that referenced
this pull request
Sep 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_failuresoption in your matrix build (more information about this in the link above).Also,
nightlyand3.7-devmay be a bit too recent/unstable so I can remove then if need be.More information about how this PR happened on https://github.com/SylvainDe/CIthon .