[issue2485] Traceback changed in 2.6 for unhashable objects

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

In 2.5, the fact that list was unhashable was checked in the list
object, and that message was hardcoded there.  In 2.6, the check for
unhashableness uses generic code, and the resulting error substitutes
the type name into the message.  This message already existed and was
used for other types, the difference between 2.5 and 2.6 is that list is
now covered by the generic code and is not a special case.

So, yes, this was intentional and no, it isn't going to get changed.

----------
components: +Interpreter Core
nosy: +bitdancer
priority:  -> low
resolution:  -> wont fix
stage:  -> committed/rejected
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue2485>
_______________________________________