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

Exclude Python version 3.6 in CI #428

Closed
LauWien opened this issue Jan 3, 2022 · 1 comment · Fixed by #435
Closed

Exclude Python version 3.6 in CI #428

LauWien opened this issue Jan 3, 2022 · 1 comment · Fixed by #435
Assignees
Labels
ci Continuous integration
Milestone

Comments

@LauWien
Copy link
Contributor

LauWien commented Jan 3, 2022

With issue actions/runner-images#4060 macOS-latest workflows will use macOS-11, saying "EOL Python versions were deprecated" and the end-of-life of Python version 3.6 being the 23rd of December 2021, using Python version 3.7 instead of 3.6 might make sense. Possible also in message_ix.

@LauWien LauWien added the ci Continuous integration label Jan 3, 2022
@LauWien LauWien self-assigned this Jan 3, 2022
@LauWien LauWien changed the title Deprecate Python version 3.6 in CI Exclude Python version 3.6 in CI Jan 3, 2022
@khaeru
Copy link
Member

khaeru commented Jan 3, 2022

The README for actions/setup-python seems to indicate that earlier versions will continue to be available; they'll just not be pre-installed on the runners. This means the setup-python action will need to download and install 3.6, which might be a little slower. At least, that's my interpretation; we should see if that does work on the macos-11 runners.

In general, the policy is:

  • The minimum Python version for ixmp can't be earlier than the minimum Python version of its mandatory dependencies (or their mandatory dependencies).
  • When those packages remove support or enforce a minimum version, we also remove support.
  • We try our best (within reason) to test the minimum version (per the above 2 points) on CI.

@khaeru khaeru added this to the 3.5 milestone Feb 8, 2022
@khaeru khaeru linked a pull request Feb 8, 2022 that will close this issue
4 tasks
@khaeru khaeru self-assigned this Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants