R. David Murray rdmur...@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.
Benjamin Peterson benja...@python.org added the comment:
Error messages are not part of the API.
--
nosy: +benjamin.peterson
resolution: wont fix - invalid
status: pending - closed
___
Python tracker rep...@bugs.python.org
New submission from Martin Geisler [EMAIL PROTECTED]:
The traceback message given when trying to hash unhashable objects has
changed from Python 2.5 to 2.6:
Python 2.5.2a0 (r251:54863, Feb 10 2008, 01:31:28)
hash([])
Traceback (most recent call last):
File stdin, line 1, in module
