New submission from STINNER Victor <victor.stin...@gmail.com>: The bpo-32043 added a new "developer mode" enabled with the new -X dev command line option.
I propose to enable asyncio debug mode with the global Python "developer mode". If an asyncio application is correctly written, the single side effect of -X dev would be to log "Executing ... took ... seconds" if a handle took longer than 100 ms. Well, a handle should *not* take longer than 100 ms. So maybe it's ok to start logging such events in the "developer mode", no? Example with attached block_loop.py script which blocks the event loop. (1) This command doesn't display anything: haypo@selma$ ./python block_loop.py (2) In developer mode, the warning a emitted to warn the developer about the bug: $ ./python -X dev block_loop.py Executing <Task finished coro=<block_loop() done, defined at block_loop.py:4> result=None created at /home/haypo/prog/python/master/Lib/asyncio/base_events.py:444> took 1.002 seconds ---------- components: asyncio files: block_loop.py messages: 306353 nosy: haypo, yselivanov priority: normal severity: normal status: open title: asyncio: enable debug mode when -X dev is used versions: Python 3.7 Added file: https://bugs.python.org/file47269/block_loop.py _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32047> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
