[issue36373] Deprecate explicit loop parameter in all public asyncio APIs
Karthikeyan Singaravelan
report at bugs.python.org
Tue Sep 10 09:43:40 EDT 2019
Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:
Few more tests and call sites
./python.exe -Wall -m test test_asyncio
Run tests sequentially
0:00:00 load avg: 2.41 [1/1] test_asyncio
/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/asyncio/locks.py:335: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
lock = Lock(loop=self._loop)
test_asyncio passed in 1 min 38 sec
== Tests result: SUCCESS ==
1 test OK.
Total duration: 1 min 38 sec
Tests result: SUCCESS
call sites
>>> list(asyncio.tasks.as_completed([asyncio.ensure_future(asyncio.sleep(1))]))
/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/asyncio/tasks.py:579: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
done = Queue(loop=loop)
/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/asyncio/queues.py:48: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
self._finished = locks.Event(loop=self._loop)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36373>
_______________________________________
More information about the Python-bugs-list
mailing list