-
-
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
Fix import under PyPy 3.8/3.9 on Windows #7850
Conversation
OK https://github.com/aio-libs/aiohttp/actions/runs/6914844384/job/18813153994?pr=7850 reproduces the issue. Now pushing a commit to try to fix it. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #7850 +/- ##
=======================================
Coverage 97.40% 97.40%
=======================================
Files 106 106
Lines 32164 32164
Branches 3739 3739
=======================================
Hits 31329 31329
Misses 631 631
Partials 204 204
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Well, we can probably merge the fix in here. But, maybe need to consider another PR to add Pypy-Windows to the CI, looks like there are a few other failing tests which will need to be fixed or skipped. |
@AlexWaygood pointed out that 3.8 is EOL so I switched CI back to pypy3.9. If we're lucky, that also makes some of the other errors go away. I saw two categories of errors in the CI run with Windows PyPy 3.8:
That seems like a bug in pypy. Possibly can be worked around by not using sendfile() on Windows PyPy.
There are also some other errors with less clear causes (e.g. On 3.9 the symlink errors went away but the Overlapped one are still around. I'll switch this PR back to running CI on Linux, and open an issue about Windows PyPy support. |
OK this is ready. There are some other CI failures on 3.11 or 3.12 but they don't look related. |
The PR title should probably change ;) |
Backport to 3.9: 💚 backport PR created✅ Backport PR branch: Backported as #7854 🤖 @patchback |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #7855 🤖 @patchback |
FTR there are a number of issues with this exception reported but unclear causes happening under normal CPython (like #4581). So I ended up releasing v3.9.4rc0 that attaches those causes to the exceptions when they are raised (via #8049 and #8089). |
Fixes #7848.