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

Don't test against python 3.7 in ci #447

Closed
wants to merge 1 commit into from
Closed

Don't test against python 3.7 in ci #447

wants to merge 1 commit into from

Conversation

maffoo
Copy link
Contributor

@maffoo maffoo commented Oct 3, 2024

Python 3.7 is no longer available for ubuntu-latest, so drop it from the ci matrix. I've also added explicit setup-python steps for any job that needs to use pip, since python 3.12 on the current version of ubuntu-latest fails when trying to install in a system package directory. This is somewhat related to #445, though there may be other things we need to do in order to drop support for older pythons.

Also explicitly setup python for any job that needs to use pip, since
python 3.12 on the latest ubuntu fails when trying to install in a
system package directory.
@davidhewitt
Copy link
Member

I'm confused by the observation that it's unavailable, because 3.7 installs fine in the PyO3 CI: https://github.com/PyO3/pyo3/actions/runs/11152546510/job/30998379433#step:3:17

@davidhewitt
Copy link
Member

That said, I would be happy if we added a runtime check for minimum Python version of 3.9, if we were to complete things in the spirit of #445. (And we should mention in the CHANGELOG.)

@maffoo
Copy link
Contributor Author

maffoo commented Oct 4, 2024

Not sure why this was failing for me, but glad to see that python 3.7 is still working in ci. I will close this, and we can address bumping the minimum supported python version separately.

@maffoo maffoo closed this Oct 4, 2024
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