Message364101
| Author | vstinner |
|---|---|
| Recipients | fabioz, vstinner |
| Date | 2020-03-13.15:48:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1584114518.95.0.177614905944.issue35370@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> PyEval_SetTrace() and PyEval_SetProfile() function have no return value but can raise an exception. I'm not comfortable about these functions. Maybe one option would be to call PyErr_WriteUnraisable() on PySys_Audit() error. It might be better than "leaking" an exception which is unexpected to PyEval_SetTrace() and PyEval_SetProfile() callers. I wrote PR 18977 to implement this idea. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-03-13 15:48:38 | vstinner | set | recipients: + vstinner, fabioz |
| 2020-03-13 15:48:38 | vstinner | set | messageid: <1584114518.95.0.177614905944.issue35370@roundup.psfhosted.org> |
| 2020-03-13 15:48:38 | vstinner | link | issue35370 messages |
| 2020-03-13 15:48:38 | vstinner | create | |