[issue1598083] Top-level exception handler writes to stdout unsafely

Change by Irit Katriel : -- stage: needs patch -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue1598083] Top-level exception handler writes to stdout unsafely

Irit Katriel added the comment: I think this can be closed as out of date because PyFile_WriteString/Object no longer use puts and they do check for errors. The error checking of PyFile_WriteString/Object in the traceback display code was the subject of Issue45635. -- nosy:

[issue1598083] Top-level exception handler writes to stdout unsafely

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Antoine Pitrou added the comment: This is certainly a low-priority issue, as it will almost never happen in practice. -- nosy: +pitrou priority: high - low stage: test needed - needs patch versions: +Python 3.4 ___ Python tracker

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Serhiy Storchaka storch...@gmail.com: -- Removed message: http://bugs.python.org/msg162876 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: -serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___ ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Georg Brandl ge...@python.org: -- assignee: georg.brandl - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___ ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Serhiy Storchaka storch...@gmail.com added the comment: It looks like another reason to replace codecs.open on io.open. -- nosy: +storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.3 -Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Alexander Belopolsky belopol...@users.sourceforge.net added the comment: I don't see anything easy in this issue. Error handling in exception or signal handlers is quite tricky. I don't see this as a high priority either, but will leave this for others to decide. -- keywords: -easy

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___ ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Daniel Diniz aja...@gmail.com: -- stage: - test needed type: - behavior versions: +Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1598083 ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Lorenzo Stoakes added the comment: Surely it's not a good idea to attempt to generate an exception within an exception handler, couldn't this lead to an infinite loop scenario? The checks prior to fputs() handle any errors by calling err_closed() and returning -1. I suggest we do the same for

[issue1598083] Top-level exception handler writes to stdout unsafely

Jean-Paul Calderone added the comment: The attached patch doesn't fix the issue I described: * err_closed() will raise an exception indicated the file is closed. However, the file is not necessarily closed, so this exception is wrong. * Most or all PyFile_WriteString callers are still not

[issue1598083] Top-level exception handler writes to stdout unsafely

Lorenzo Stoakes added the comment: Ok, thankyou for your feedback, I will take another look at it. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _ ___

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by A.M. Kuchling: -- keywords: +easy _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1598083] Top-level exception handler writes to stdout unsafely

Changes by Christian Heimes: -- versions: +Python 2.6 _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1598083] Top-level exception handler writes to stdout unsafely

Georg Brandl added the comment: I'll look into it. -- nosy: +georg.brandl _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _ ___ Python-bugs-list mailing

[issue1598083] Top-level exception handler writes to stdout unsafely

Sean Reifschneider added the comment: I don't suppose you could wrangle up a proposed patch to fix this? -- nosy: +jafo _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _

[issue1598083] Top-level exception handler writes to stdout unsafely

Jean-Paul Calderone added the comment: Not likely, given the number of things on my plate already. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1598083 _ ___