[issue6709] It's possible to create TryExcept with no handlers

Changes by Ezio Melotti : -- stage: needs patch -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue6709] It's possible to create TryExcept with no handlers

Benjamin Peterson added the comment: This was fixed a while ago: Traceback (most recent call last): File "", line 1, in ValueError: Try has neither except handlers nor finalbody -- resolution: -> out of date status: open -> closed ___ Python trac

[issue6709] It's possible to create TryExcept with no handlers

Changes by Ezio Melotti : -- nosy: +brett.cannon, georg.brandl, ncoghlan stage: -> needs patch versions: +Python 3.3, Python 3.4 -Python 3.1 ___ Python tracker ___ __

[issue6709] It's possible to create TryExcept with no handlers

Changes by Mark Lawrence : -- versions: -Python 2.5, Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6709] It's possible to create TryExcept with no handlers

Changes by Benjamin Peterson : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6709] It's possible to create TryExcept with no handlers

New submission from Benjamin Peterson : I think we might need to devise some way to add custom validation when AST is being compiled. For example, you can also pass a level to ImportFrom which is < -1. >>> x = ast.parse("try: x\nexcept y: pass") >>> del x.body[0].handlers[:] >>> compile(x, "", "