Skip to content

Stop running Python 3.5 in CI - #10345

Merged
hauntsaninja merged 2 commits into
python:masterfrom
hauntsaninja:ci35
Apr 21, 2021
Merged

hauntsaninja merged 2 commits into
python:masterfrom
hauntsaninja:ci35

Conversation

@hauntsaninja

@hauntsaninja hauntsaninja commented Apr 20, 2021 •

Copy link
Copy Markdown
Collaborator

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

@emmatyping emmatyping left a comment

Copy link
Copy Markdown
Member

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
Copy Markdown
Collaborator

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

@hauntsaninja

Copy link
Copy Markdown
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
Copy Markdown
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

@hauntsaninja
hauntsaninja requested a review from TH3CHARLie April 21, 2021 01:53

@TH3CHARLie TH3CHARLie left a comment

Copy link
Copy Markdown
Collaborator

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

JukkaL commented Apr 21, 2021

Copy link
Copy Markdown
Collaborator

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