[issue36829] CLI option to make PyErr_WriteUnraisable abortthe current process

Thomas Grainger added the comment: > this option should be used exclusively for debugging user extension modules. I have a very large codebase that fires the odd ResourceWarning, and after fixing them all I'd like to ensure that they do not reoccur. When using `-W error` it still won't fail

[issue36829] CLI option to make PyErr_WriteUnraisable abortthe current process

Serhiy Storchaka added the comment: It looks like a good idea to me. But it should not be -W error. It should be an -X option, and this option should be used exclusively for debugging user extension modules. -- nosy: +vstinner ___ Python tracker

[issue36829] CLI option to make PyErr_WriteUnraisable abortthe current process

Stéphane Wirtel added the comment: Hi Serhiy, What do you think about this idea? Normally, we could use -W error when there is an exception. -- nosy: +matrixise, serhiy.storchaka ___ Python tracker

[issue36829] CLI option to make PyErr_WriteUnraisable abortthe current process

New submission from Thomas Grainger : Currently it's quite easy for these errors to go unnoticed. I'd like a way to easily detect these in CI. nedbat suggested piping the process output to another tool, and looking for 'Exception ignored in:' but this seems a little diff --