Message256618
| Author | yselivanov |
|---|---|
| Recipients | georg.brandl, gvanrossum, larry, ncoghlan, oconnor663, serhiy.storchaka, vstinner, yselivanov |
| Date | 2015-12-17.22:58:06 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1450393086.92.0.687956932606.issue25782@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
A new patch is attached. Please review. I decided to remove the fix for recursive __cause__. Currently, `raise e from e` doesn't cause any problem, and if we fix the interpreter to raise an RuntimeError in such cases it will be a backwards incompatible change. I don't see any point in introducing such a change in a bugfix Python release. We can open a separate issue for 3.6 though. Fixing __context__ in 3.5.2 is way more important, since the interpreter can actually infinitely loop itself in some places. And since there is no syntax for setting __context__ manually (as opposed to __cause__ via raise .. from), I suspect that there will be much less people affected by this fix. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-12-17 22:58:06 | yselivanov | set | recipients: + yselivanov, gvanrossum, georg.brandl, ncoghlan, vstinner, larry, serhiy.storchaka, oconnor663 |
| 2015-12-17 22:58:06 | yselivanov | set | messageid: <1450393086.92.0.687956932606.issue25782@psf.upfronthosting.co.za> |
| 2015-12-17 22:58:06 | yselivanov | link | issue25782 messages |
| 2015-12-17 22:58:06 | yselivanov | create | |