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 terry.reedy
Recipients amaury.forgeotdarc, benjamin.peterson, pitrou, terry.reedy, yury
Date 2011-12-24.23:07:49
SpamBayes Score 4.0641213e-11
Marked as misclassified No
Message-id <1324768070.71.0.978471220055.issue6028@psf.upfronthosting.co.za>
In-reply-to
Content
I believe #3555, #7338, and *13644 are basically duplicates of this issue. I have left this one open because it has a try at a patch. I think any patch should be tested with the other examples.

I agree with Antoine that an intentional exit is not a crash.
I also agree that the current procedure is not really a bug either. According to the language spec, the interpreter should recurse forever;-), just like "while True: pass" iterates 'forever'. Given that it does not due to finite limitations, the exact alternate behavior is undefined.

Now, if someone can find a way to better handle infinite recursion mixed with exceptions, without re-introducing real crashes or eliminating the benefits of the 3.0 changes, great.

Yury, I think Antoine's point is that gracefully handling all the different kinds of programming mistakes in a finite system is a delicate and difficult balancing act.
History
Date User Action Args
2011-12-24 23:07:50terry.reedysetrecipients: + terry.reedy, amaury.forgeotdarc, pitrou, benjamin.peterson, yury
2011-12-24 23:07:50terry.reedysetmessageid: <1324768070.71.0.978471220055.issue6028@psf.upfronthosting.co.za>
2011-12-24 23:07:50terry.reedylinkissue6028 messages
2011-12-24 23:07:49terry.reedycreate