[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: The output will be fixed by #38986 Nothing to do here. -- resolution: -> works for me stage: -> resolved status: open -> closed ___ Python tracker

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: Slower by percents, not in the factor of times. I guess for tests it is satisfactory. -- ___ Python tracker ___

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Wei-Cheng Pan added the comment: I cannot import asyncio.task, so I did this instead: import asyncio.tasks asyncio.tasks.Task = asyncio.tasks._PyTask Then it changed to this: Executing wait_for= created at /.../lib/python3.8/unittest/async_case.py:118> took 0.187 seconds I suppose this

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: I've assigned myself to never forget about the issue; if somebody wants to fix _CTask and TaskWakeupMethWrapper representation -- you are welcome -- assignee: -> asvetlov ___ Python tracker

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: Thanks for the clarification. I forgot about this thing; the output can be improved sure. As a workaround you can use the following hack:: import asyncio.task asyncio.task.Task = asyncio.task._PyTask IIRC the pure python version prints a coroutine name at

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Wei-Cheng Pan added the comment: Executing () created at /.../lib/python3.8/asyncio/queues.py:70> took 0.104 seconds Executing () created at /.../lib/python3.8/asyncio/queues.py:70> took 0.121 seconds I was expecting it can display the stack of the awaitable. --

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: At first, would be nice to figure out what "invalid line reported" does mean. What text is reported and what is expected? -- ___ Python tracker

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Callum Ward added the comment: Hi, is there anything that needs to be fixed or done here? -- nosy: +callumquick ___ Python tracker ___

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: Well, if the reported line is invalid it should be fixed -- ___ Python tracker ___ ___

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Change by Andrew Svetlov : -- components: +asyncio nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Wei-Cheng Pan added the comment: > Usually, it is a sign of a problem in user code, e.g. something should be > pushed into executor. Sometimes also happens on low-end CI machines. And the message is somewhat unclear to me. I have to grep cpython sources to understand that it is coming from

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

Andrew Svetlov added the comment: This print comes from asyncio debug mode when async function is blocked by time longer than 0.1 sec (see loop.slow_callback_duration at loop.slow_callback_duration). Usually, it is a sign of a problem in user code, e.g. something should be pushed into

[issue38608] Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode

New submission from Wei-Cheng Pan : In bpo-32972 we enabled debug mode in IsolatedAsyncioTestCase._setupAsyncioLoop, which may print some warnings that are not that important to tests. (e.g. Executing took 0.110 seconds) I personally don't really like it being turn on by default, but if it