-
Notifications
You must be signed in to change notification settings - Fork 60
Python 3.10 compatibility #166
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
Conversation
9ae7819
to
e432838
Compare
Codecov Report
@@ Coverage Diff @@
## master #166 +/- ##
==========================================
- Coverage 94.27% 94.27% -0.01%
==========================================
Files 28 28
Lines 1958 1957 -1
==========================================
- Hits 1846 1845 -1
Misses 112 112
Continue to review full report at Codecov.
|
For some reason, any version of That is a problem for py310, because of pytest-dev/pytest#8540 (see https://github.com/scrapinghub/python-scrapinghub/runs/5484724225), which is available since |
I see |
|
🤦 |
Backporting the Python 3.10 fix I have been able to identify pytest-dev/pytest#3754 as the cause of the issue. Things work with the prior upstream commit. I have pushed at https://github.com/Gallaecio/pytest/tree/3.7.0-3.7.1-fork the latest working pytest with the Python 3.10 fix backported, in case you want to use that in the meantime. I will continue looking into it for a more permanent fix. |
I restored py27 and py35 support, it's not strictly necessary to remove them in order to support py310 |
Update some imports and test requirements for py310 compatibility.
Small overlap with #159, I think we can merge this sooner.