[issue24864] errors writing to stdout during interpreter exit exit with status 0

Changes by Robert Collins : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue24864] errors writing to stdout during interpreter exit exit with status 0

Robert Collins added the comment: Oh, just saw your comment Martin; yes, this does look like a dupe. -- ___ Python tracker ___ ___ Pyt

[issue24864] errors writing to stdout during interpreter exit exit with status 0

Robert Collins added the comment: This patch is a minimal stab at the issue. We should do this change because as it stands genuine user affecting errors can be masked both in pipelines and non-pipeline cases. A more comprehensive patch would also change e.g. Py_Exit, and the various other use

[issue24864] errors writing to stdout during interpreter exit exit with status 0

Martin Panter added the comment: I don’t know much about PDB, but if this is just about setting the exit code, it may be a dupe of Issue 5319. The fix proposed there is a new Py_FinalizeEx() API that returns an exit status, if I remember correctly. -- nosy: +martin.panter

[issue24864] errors writing to stdout during interpreter exit exit with status 0

Robert Collins added the comment: Updating the title to reflect my deeper understanding: the only issue here is that we don't alter the exit code. -- title: errors writing to stdout are uncatchable and exit with status 0 -> errors writing to stdout during interpreter exit exit with sta