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

updated latest Python in CI to 3.13 #6884

Merged
merged 1 commit into from
Oct 11, 2024
Merged

updated latest Python in CI to 3.13 #6884

merged 1 commit into from
Oct 11, 2024

Conversation

firewave
Copy link
Collaborator

@firewave firewave commented Oct 7, 2024

No description provided.

@firewave firewave force-pushed the py-313 branch 2 times, most recently from 8a0b587 to a212f5a Compare October 11, 2024 10:00
@firewave firewave marked this pull request as ready for review October 11, 2024 10:00
@chrchr-github
Copy link
Collaborator

According to https://devguide.python.org/versions/, anything older than 3.9 is EOL already, Do we still need to support 3.6, 3.7, 3.8?

@firewave
Copy link
Collaborator Author

According to https://devguide.python.org/versions/, anything older than 3.9 is EOL already, Do we still need to support 3.6, 3.7, 3.8?

I am going to address that in something which has a wider scope soon.

@danmar
Copy link
Owner

danmar commented Oct 11, 2024

According to https://devguide.python.org/versions/, anything older than 3.9 is EOL already, Do we still need to support 3.6, 3.7, 3.8?

I would prefer that scripts that we distribute (the addons, htmlreport) support old python versions if possible. For internal scripts (donate-cpu* , pytest, matchcompiler, reduce.py, etc) I do not have any opinions about dropping support for old python versions.

@firewave firewave merged commit 45d34fb into danmar:main Oct 11, 2024
66 checks passed
@firewave firewave deleted the py-313 branch October 11, 2024 15:18
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