Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add most recent Python versions in Travis CI #119

Merged
merged 1 commit into from
Mar 9, 2017
Merged

Add most recent Python versions in Travis CI #119

merged 1 commit into from
Mar 9, 2017

Conversation

SylvainDe
Copy link
Contributor

Add more recent Python versions including development branches and nightly build.

Related to #118 .

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 CPython ( 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).

Also, nightly and 3.7-dev may be a bit too recent/unstable so I can remove then if need be.

More information about how this PR happened : https://github.com/SylvainDe/CIthon .

More information about the various Python versions available on Travis : https://docs.travis-ci.com/user/languages/python/ .

More information about the Python 3.6 version schedule : https://www.python.org/dev/peps/pep-0494/ .
More information about the Python 3.7 version schedule : https://www.python.org/dev/peps/pep-0537/ .

Add more recent Python versions including development branches and nightly build.
@coveralls
Copy link

coveralls commented Mar 7, 2017

Coverage Status

Coverage remained the same at 89.859% when pulling 59dfc59 on SylvainDe:develop into 9be5b80 on geeknam:develop.

@SylvainDe
Copy link
Contributor Author

@mnemonicflow Should this PR be closed ? Merged ?

@alibitek alibitek merged commit 757cac9 into geeknam:develop Mar 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants