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

Stop running Python 3.5 in CI #10345

Merged
merged 2 commits into from
Apr 21, 2021
Merged

Stop running Python 3.5 in CI #10345

merged 2 commits into from
Apr 21, 2021

Conversation

hauntsaninja
Copy link
Collaborator

@hauntsaninja hauntsaninja commented Apr 20, 2021

Python 3.5 always fails in CI these days. So a) it's annoying and a bad contributor experience, b) we're effectively not testing against Python 3.5 anyway
Linking #9950

Python 3.5 always fails in CI these days
Linking python#9950
Copy link
Collaborator

@ethanhs ethanhs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I look forward to dropping support so we can use TypeVar without needing to guard it.

@TH3CHARLie
Copy link
Collaborator

Agreed. Should we keep the number of compiled suites by making 3.6 compiled?

@hauntsaninja
Copy link
Collaborator Author

You probably have a better sense of that than I do — how likely is it that 3.6 compiled will catch issues not caught by 3.7 compiled and 3.6?

@hauntsaninja
Copy link
Collaborator Author

I do seem to remember we had a CI false negative once because we didn't have a compiled >= 3.8 (due to some typeshed change to ast), so maybe we make Python 3.9 compiled

Copy link
Collaborator

@TH3CHARLie TH3CHARLie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A compiled 3.9 LGTM!

@hauntsaninja hauntsaninja merged commit ba3578a into python:master Apr 21, 2021
@hauntsaninja hauntsaninja deleted the ci35 branch April 21, 2021 03:23
@JukkaL
Copy link
Collaborator

JukkaL commented Apr 21, 2021

I think that we should run compiled tests on the earliest supported/working Python version and the latest, so it would be 3.6 and 3.9 after this change.

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.

4 participants