[issue36692] Unexpected stderr output from test_sys_settrace

Nick Coghlan added the comment: I'm not, so I assume this got cleaned up somewhere along the way. -- resolution: -> out of date stage: needs patch -> resolved status: pending -> closed ___ Python tracker

[issue36692] Unexpected stderr output from test_sys_settrace

Irit Katriel added the comment: I'm not seeing this output when I run the test. Are you still seeing it? -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue36692] Unexpected stderr output from test_sys_settrace

Philip Dye added the comment: Once consensus is reached, I would be happy to do the work. -- nosy: +Philip Dye ___ Python tracker ___

[issue36692] Unexpected stderr output from test_sys_settrace

hai shi added the comment: It looks like setstrace function trigger this codeline: https://github.com/python/cpython/blob/master/Modules/_asynciomodule.c#L2618 Looks we can use set_exception_handler() to catch this error, but i am not sure it is worth catching this error through adding a

[issue36692] Unexpected stderr output from test_sys_settrace

New submission from Nick Coghlan : The test output from test_sys_settrace makes it look like a couple of the async tracing tests aren't cleaning up after themselves properly: ``` [ncoghlan@localhost cpython]$ ./python -m test test_sys_settrace Run tests sequentially 0:00:00 load avg: 1.27