-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Patchback/backports/3.9/bd008ca646df25e043738aa85acca0d30ddcf128/pr 5898 #6373
Patchback/backports/3.9/bd008ca646df25e043738aa85acca0d30ddcf128/pr 5898 #6373
Conversation
Looks like this is a feature and should go into the next minor release. |
i.e. 3.9? That's the target. |
Test failure appears to be something already on the 3.9 branch. This PR looks good to merge. |
Looks like you confused the PR description, then. And that confused me.
Looks like aiohttp 3.9 now requires Python 3.7 but the PyPy version in the test matrix is still Python 3.6. |
Yeah, sorry, I meant the backport to 3.8 was missed (it failed and nobody did a manual backport), so I'm doing the backport to 3.9 now.
Yep, just noticed that as well in #6374 |
The version in ci.yaml only specifies 'pypy3', which I assume would always pick the latest release (although I can't find any documentation confirming that). The latest release on Ubuntu-20.04 is 3.8: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#pypy Though on Ubuntu-18.04 it's 3.6: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md#pypy But, we appear to be asking for 'ubuntu-latest', which is supposed to be 20.04. So, I'm confused what part is misconfigured... |
OK, changing to So, I think |
This is the original format (that should be deprecated at some point I think) before they added support for requesting more granular versions. Something like |
…aa85acca0d30ddcf128/pr-5898
Green finally, thank you all! |
Missed the backport to 3.9.