Noam Raphael wrote: > The alternative is to drop the __hash__ method of user-defined classes > (as Guido already decided to do), and to make the default __eq__ > method compare the two objects' __dict__ and slot members.
The question then is what hash(x) would do. It seems that you expect it then somehow not to return a value. However, under this patch, the fallback implementation (use pointer as the hash) would be used, which would preserve hash(x)==id(x). > See the thread about default equality operator - Josiah Carlson posted > there a metaclass implementing this equality operator. This will likely cause a lot of breakage. Objects will compare equal even though they conceptually are not, and even though they did not compare equal in previous Python versions. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
