New submission from Andrew Svetlov <andrew.svet...@gmail.com>:
Consider the following code:
import asyncio
q = asyncio.Queue()
async def main():
await asyncio.gather(q.put(1), q.get(1))
asyncio.run(main())
This code just hangs since run() creates a loop but queue is bound with another
(default) event loop.
The error is confusing and hard-to-debug.
We should raise a warning at least for the case; start from DeprecationWarning
and make the system stricter later.
asyncio/locks.py is also affected since it has first-class classes (classes
that instantiated by a user directly without factories).
----------
components: asyncio
messages: 355449
nosy: asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Deprecate creation of asyncio object when the loop is not running
versions: Python 3.9
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
