-
Notifications
You must be signed in to change notification settings - Fork 288
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: Test on Python 3.10, bump actions versions #2895
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Posted my comment at #2894 (comment), but meant to do it here:
It doesn't seem to be new pip. Installing pip 22.1 in a Python 3.7 environment produces the same issue for me. I think there must be something in the dependency chain that's causing a resolution failure in 3.7. Pip's resolution mechanism is to find older and older versions of a tool, and we eventually found a nitime that is so old that it imports the entire module and breaks because numpy isn't a build dependency.
I think the thing to do is to drop Python 3.7. NEP29 recommended dropping it almost a year ago, and I assume that what we're seeing is the consequences of the broader ecosystem no longer testing on it. It's probably not worth a lot of effort tracking this down.
I would suggest we take one of the following routes:
- Adhere to NEP29 and drop Python minor releases along with the rest of the ecosystem.
- Continue testing and advertise support for non-EOL Pythons until the fixes become non-obvious.
6b4db58
to
2895424
Compare
eb5effb
to
210086c
Compare
Skipping over Circle builds. |
No description provided.