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

CI: switch testing to Python 3.10+ #143

Merged
merged 1 commit into from
Aug 27, 2024

Conversation

ptoscano
Copy link
Contributor

@ptoscano ptoscano commented Aug 14, 2024

Test the more recent versions of Python, to ensure Betelgeuse works
also with these versions. The oldest versions are dropped, leaving only
the latest 3 versions of Python.

Copy link
Member

@ogajduse ogajduse left a comment

Choose a reason for hiding this comment

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

@ptoscano I would keep only the latest three versions unless you are using an older version of Python than 3.10.

@ptoscano
Copy link
Contributor Author

@ptoscano I would keep only the latest three versions unless you are using an older version of Python than 3.10.

ah, so should I move the window of supported versions from 3.8-3.10 to 3.10-3.12?

@ogajduse
Copy link
Member

If your team does not require 3.8 and 3.9 support, please move the window.

Test the more recent versions of Python, to ensure Betelgeuse works
also with these versions. The oldest versions are dropped, leaving only
the latest 3 versions of Python.
@ptoscano ptoscano changed the title CI: test also Python 3.11 and 3.12 CI: switch testing to Python 3.10+ Aug 26, 2024
@ptoscano
Copy link
Contributor Author

ACK, done so.

@ogajduse
Copy link
Member

Thank you, @ptoscano!

@ogajduse ogajduse merged commit ec48bd0 into SatelliteQE:master Aug 27, 2024
3 checks passed
@ptoscano ptoscano deleted the ci-new-pythons branch August 27, 2024 06:30
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.

2 participants