Ezio Melotti ezio.melo...@gmail.com added the comment:
A FAQ entry could be added to explain this error, like we already do for the
UnboundLocalError:
http://docs.python.org/faq/programming.html#why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value
--
nosy: +ezio.melotti
Terry J. Reedy tjre...@udel.edu added the comment:
Stephen is right; this sort of guess-the-bug heuristic is out of scope for the
CPython interpreter. I believe you grossly under estimate the difficulty of
such a this. Consider that idea rejected.
What *is* disconcerting is the exact form of
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
title: In TypeError: 'tuple' object is not callable, suggest a comma. - In
TypeError: 'tuple' object is not callable, explain that a comma may be missing
___
Python tracker
Steven D'Aprano steve+pyt...@pearwood.info added the comment:
I think this suggested enhancement is unreasonable and of limited usefulness,
and even if it were useful, too specialised to bother with.
The obvious message is badly misleading. When I read this:
TypeError: 'tuple' object is not
Ben Longbons b.r.longb...@gmail.com added the comment:
This kind of debug your code is the kind of thing I've gotten used to from
the Clang C/C++ compiler. Granted, compiled languages have an advantage here,
but enough residual information remains for the interpreter at runtime.
And I am in
