Message 66580 - Python tracker

➜

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	brunogola
Recipients	belopolsky, brunogola
Date	2008-05-10.20:02:55
SpamBayes Score	0.0012262928
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
Should nested tuples in an except clause be a valid syntax? like: ... except ((ValueError, Exception), TypeError, (...)): pass I don't see any benefit and because of this behavior the implementation (in Python/errors.c and in the patch attached) will use recursive function. I think that any objects inside a tuple in an except clause should be treated equally (as an object), even a tuple, so the except clause above should be an error in py3k and should produce a warning because the list objects does not inherits BaseException. Please, see my comment in http://bugs.python.org/issue2345, it is related to this issue.

Should nested tuples in an except clause be a valid syntax?
like:
...
except ((ValueError, Exception), TypeError, (...)):
    pass

I don't see any benefit and because of this behavior the implementation
(in Python/errors.c and in the patch attached) will use recursive function. 

I think that any objects inside a tuple in an except clause should be
treated equally (as an object), even a tuple, so the except clause above
should be an error in py3k and should produce a warning because the list
objects does not inherits BaseException.

Please, see my comment in http://bugs.python.org/issue2345, it is
related to this issue.

History
Date	User	Action	Args
2008-05-10 20:02:57	brunogola	set	spambayes_score: 0.00122629 -> 0.0012262928 recipients: + brunogola, belopolsky
2008-05-10 20:02:56	brunogola	set	spambayes_score: 0.00122629 -> 0.00122629 messageid: <[email protected]>
2008-05-10 20:02:56	brunogola	link	issue2380 messages
2008-05-10 20:02:55	brunogola	create