You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have official support for Python 3.10.
The main issue I see is that the loop parameter in the high-level asyncio APIs, deprecated since 3.8, is removed in 3.10. These are still used in quite a few places.
It’s not easy for me to run the full test suite, so it’s hard for me to know whether or not simply removing all such loop parameters without further changes to the code would fix Python 3.10 support without breaking anything on some older Python version that you still support.
The text was updated successfully, but these errors were encountered:
Hi @musicinmybrain
Thanks for bringing this to our notice. I see that the potential impact of this API change could be in the async_context which uses asyncio.
We will have the change tested on our end soon to address the compatibility with Python 3.10.
I see that the potential impact of this API change could be in the async_context which uses asyncio.
Maybe an API change is not necessary. In async_context.py, loop is passed to asyncio.current_task(), which still accepts a loop argument as of Python 3.10.
It would be nice to have official support for Python 3.10.
The main issue I see is that the
loop
parameter in the high-levelasyncio
APIs, deprecated since 3.8, is removed in 3.10. These are still used in quite a few places.It’s not easy for me to run the full test suite, so it’s hard for me to know whether or not simply removing all such
loop
parameters without further changes to the code would fix Python 3.10 support without breaking anything on some older Python version that you still support.The text was updated successfully, but these errors were encountered: