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 Mark.Shannon
Recipients Demur Rumed, Mark.Shannon, benjamin.peterson, christian.heimes, mark.dickinson, nascheme, ncoghlan, pitrou, rhettinger, serhiy.storchaka, trent
Date 2017-12-05.11:11:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <b5f64487-0d20-76bf-9f33-b6017022c10a@hotpy.org>
In-reply-to <1512409988.04.0.213398074469.issue17611@psf.upfronthosting.co.za>
Content
On 04/12/17 17:53, Neil Schemenauer wrote:

> There is a bug with the PR regarding the final bodies.  Exits from the final body cause the whole fblock stack to unwind, not just the blocks enclosing the final body.  Unwind looks at 'c' to get the fblock stack. I think we need to allocate fblockinfo on the C stack and then use a back pointer to enclosing block.  When you get into a final body that creates its own fblockinfo (e.g. a try/except inside the finally), the current code doesn't work.

I don't really follow you.
Could you provide a code example that will expose this error?
History
Date User Action Args
2017-12-05 11:11:58Mark.Shannonsetrecipients: + Mark.Shannon, nascheme, rhettinger, mark.dickinson, ncoghlan, pitrou, christian.heimes, benjamin.peterson, trent, serhiy.storchaka, Demur Rumed
2017-12-05 11:11:58Mark.Shannonlinkissue17611 messages
2017-12-05 11:11:58Mark.Shannoncreate