Message335927
| Author | vstinner |
|---|---|
| Recipients | SamB, eryksun, foom, gregory.p.smith, jwilk, loewis, martin.panter, mwh, petri.lehtinen, pitrou, rnk, vstinner |
| Date | 2019-02-19.11:35:52 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1550576152.63.0.788573048941.issue1054041@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> if (PyOS_setsig(SIGINT, SIG_DFL) == SIG_ERR) {
> perror("signal"); /* Impossible in normal environments. */
In my experience, Python is were impossible things happen. Would it be possible to write a better error message to explain what happened?
I expect that if PyOS_setsig() fails, the user cannot do much for that. It may be a bug in the libc and so cannot be fixed easily. Maybe we should simply ignore the error? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-02-19 11:35:52 | vstinner | set | recipients: + vstinner, mwh, loewis, gregory.p.smith, foom, pitrou, jwilk, rnk, petri.lehtinen, martin.panter, SamB, eryksun |
| 2019-02-19 11:35:52 | vstinner | set | messageid: <1550576152.63.0.788573048941.issue1054041@roundup.psfhosted.org> |
| 2019-02-19 11:35:52 | vstinner | link | issue1054041 messages |
| 2019-02-19 11:35:52 | vstinner | create | |