Message291825
| Author | larsonreever |
|---|---|
| Recipients | Rotem Yaari, Yury.Selivanov, georg.brandl, gregory.p.smith, gvanrossum, larry, larsonreever, ncoghlan, oconnor663, python-dev, serhiy.storchaka, terry.reedy, vstinner, yselivanov |
| Date | 2017-04-18.07:14:21 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1492499662.29.0.47345004412.issue25782@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
My patch works for your example too. Since it checks for loops in __context__ setter, you shouldn't be able to create complicated loops. However, since PyException_SetContext and PyException_SetCause are public APIs, and their return type is 'void', I can't raise an error when a C code introduces a cycle, in that case, the exc->cause/exc->context will be set to NULL.(I came to this bug via the ExitStack + subprocess issue27122 which merely has a suggested workaround patch as a band aid that might help until this is fixed) Thanks: http://driverwhiz.com/device-drivers |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-18 07:14:22 | larsonreever | set | recipients: + larsonreever, gvanrossum, georg.brandl, terry.reedy, gregory.p.smith, ncoghlan, vstinner, larry, Yury.Selivanov, python-dev, serhiy.storchaka, yselivanov, oconnor663, Rotem Yaari |
| 2017-04-18 07:14:22 | larsonreever | set | messageid: <1492499662.29.0.47345004412.issue25782@psf.upfronthosting.co.za> |
| 2017-04-18 07:14:22 | larsonreever | link | issue25782 messages |
| 2017-04-18 07:14:21 | larsonreever | create | |