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 DivinityArcane
Recipients DivinityArcane
Date 2013-01-11.02:06:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357869986.79.0.0900594167753.issue16924@psf.upfronthosting.co.za>
In-reply-to
Content
When running multiple nested loops (to emulate the circumstances of a program running multiple different modules at once,) each with their own try: except: block (in this case for KeyboardInterrupt,) the order of operations seems to fall out of place. As you can see in the screenshot, even though the inner-most loop should never have been left (or ended for that matter,) the parent loop catches the exception in its place on occasion. While this isn't necessarily a huge issue, for certain things it can be rather annoying and downright confusing. For most all other languages, for example, the inner-most loop would, of course, catch the exception first.

Requesting more insight on this issue.
History
Date User Action Args
2013-01-11 02:06:26DivinityArcanesetrecipients: + DivinityArcane
2013-01-11 02:06:26DivinityArcanesetmessageid: <1357869986.79.0.0900594167753.issue16924@psf.upfronthosting.co.za>
2013-01-11 02:06:26DivinityArcanelinkissue16924 messages
2013-01-11 02:06:24DivinityArcanecreate