This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients vstinner, yselivanov
Date 2017-11-16.11:50:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510833052.89.0.213398074469.issue32047@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2017-11-16 11:50:52vstinnersetrecipients: + vstinner, yselivanov
2017-11-16 11:50:52vstinnersetmessageid: <1510833052.89.0.213398074469.issue32047@psf.upfronthosting.co.za>
2017-11-16 11:50:52vstinnerlinkissue32047 messages
2017-11-16 11:50:52vstinnercreate