-
Notifications
You must be signed in to change notification settings - Fork 62
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 deprecation warning that appear in Python 3.8+ #203
Comments
Hi @muriloviana - Adding support for 3.8 sounds good to me. Although I haven't tried running You are more than welcome to work on this if you have the bandwidth. Let me know if decide to take this one on. Thanks! |
collections related warning has been further delayed to Python 3.10 |
Cool, I'm going to work on that. |
The change has been merged in Python 3.10 : python/cpython#23754 |
I ran the project under 3.9 and I don't see any errors. There are several warnings that the project might break in Python 3.10. Also Python 3.8 has been added to travis in https://github.com/prkumar/uplink/pull/186/files so I guess python 3.8 is supported. collections related warnings have been fixed in #201
|
ping |
Hi @kamil-zabierek - official support for 3.8+ was introduced in the latest release, v0.9.5. If you are encountering an issue with using the library with Python 3.8+, could you share some details? |
i just started project with uplink dependency (py3.9) and i can see deprecation warnings. |
Oh, I see... Those deprecation warnings should not cause issues for your usage of uplink with py3.9. The presence of deprecation warnings does not mean that the library doesn't support the current python version. It just indicates that the uplink version you are using will not support a future python version that removes the deprecated feature. Hence, your original comment sort of confused me, since I interpreted it as suggesting that uplink was broken for py3.8+. Instead, it seems rather that you are put off by the warnings appearing in the console, which is totally understandable. I can understand how these warnings can cause trepidation for newcomers that see them and want to run the other way. To that end, I believe your concerns will be addressed once we remove our usage of |
I've submitted #248, which removes all "@asyncio.coroutine" usage in the library. |
I'm planning on releasing the change with v0.9.6 on Monday evening PST |
All |
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Would be very welcome if we add support for Python 3.8.
Additional context
I can work on it if necessary.
The text was updated successfully, but these errors were encountered: