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 vstinner
Recipients berker.peksag, christian.heimes, ezio.melotti, felipecruz, jcon, mrshu, serhiy.storchaka, vstinner
Date 2013-01-10.22:19:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
./Python/traceback.c:            write(fd, &c, 1);
./Python/traceback.c:        write(fd, "\"", 1);
./Python/traceback.c:        write(fd, "\"", 1);
./Python/traceback.c:    write(fd, "\n", 1);
./Python/traceback.c:            write(fd, "\n", 1);

Oh, I wrote these ones. It is code called by the faulthandle module, from a signal handler. So only async-safe functions can be called (no thread, no memory allocation, no lock!, etc.).

A simple fix would be to mark that we don't care if write() fails, but (void)write(fd, ...); doesn't make the warning quiet.
Date User Action Args
2013-01-10 22:19:02vstinnersetrecipients: + vstinner, christian.heimes, ezio.melotti, felipecruz, jcon, berker.peksag, serhiy.storchaka, mrshu
2013-01-10 22:19:02vstinnersetmessageid: <>
2013-01-10 22:19:02vstinnerlinkissue15948 messages
2013-01-10 22:19:01vstinnercreate