-
Notifications
You must be signed in to change notification settings - Fork 463
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
Test with Python 3.9 - look for deprecation #910
Comments
I will like to work on this. |
@Nirali0029 Feel free! Let us know if you hit any snags. |
Python 3.9 is the last version providing backward compatibility layers. |
@chazuttu Ooh, good find. I'll open a separate issue to get that fixed. |
I have tried to test on Ubuntu 20.04 with Python 3.9 in venv (in WSL :D) and encountered some problems. When doing Error
There are other people facing this on Python 3.9 (one, two, three). My error is not exactly the same and most of the others were on macOS but I'm pretty sure it's Python 3.9 problem. pycares and aiodns have same maintainer and it looks like they no longer have time for those projects (pycares, aiodns), so it is unclear when this will be resolved. It's possible that a relatively easy solution might be found (seems like macOS folks were able to fix it tinkering with c-ares) but I haven't looked into it. |
In a follow up to my previous message: installing All necessary bits are already present in GitHub-hosted runners so Python 3.9 should work in CI here. I've added it to the workflow (both Ubuntu and Windows) and it passed all tests (haven't run long tests though). See here. P.S. Also tested on Python 3.10, Ubuntu tests fail inside |
I think with the addition of pyupgrade in #1147 that it's safe to close this. I expect to do another round of double checking before we start officially supporting 3.9 but that's not on the radar for the 2.1 release at this time. |
Python 3.9 is coming, and some of the things we're using specifically in the tests may have been deprecated. To do this, you'll probably want to install python 3.9 and set up a separate venv to test it. Report anythign found back into this issue.
The text was updated successfully, but these errors were encountered: