New submission from Justin Eittreim: 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. ---------- components: None files: 2013-01-10 17_55_13-Python Shell.png messages: 179613 nosy: DivinityArcane priority: normal severity: normal status: open title: try: except: ordering error type: behavior versions: Python 3.3 Added file: http://bugs.python.org/file28682/2013-01-10 17_55_13-Python Shell.png _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16924> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
