This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author iritkatriel
Recipients iritkatriel
Date 2021-10-27.21:27:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1635370026.46.0.0220648873339.issue45635@roundup.psfhosted.org>
In-reply-to
Content
They do things like 

    err = PyFile_WriteString("TypeError: print_exception(): Exception expected for value, ", f);
    err += PyFile_WriteString(Py_TYPE(value)->tp_name, f);
    err += PyFile_WriteString(" found\n", f);

which means that PyFile_XXX functions are called after error. They should return (abort printing the exception) instead.


It gets even more interesting with PyFile_WriteObject calls - this function asserts that the exception is not set, so the code calls PyErr_Clear() before calling PyFile_WriteObject(). It should avoid making the call altogether.
History
Date User Action Args
2021-10-27 21:27:06iritkatrielsetrecipients: + iritkatriel
2021-10-27 21:27:06iritkatrielsetmessageid: <1635370026.46.0.0220648873339.issue45635@roundup.psfhosted.org>
2021-10-27 21:27:06iritkatriellinkissue45635 messages
2021-10-27 21:27:06iritkatrielcreate