A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133284.html below:

[Python-Dev] Intricacies of calling __eq__

[Python-Dev] Intricacies of calling __eq__ [Python-Dev] Intricacies of calling __eq__Antoine Pitrou solipsis at pitrou.net
Wed Mar 19 16:07:16 CET 2014 
On Wed, 19 Mar 2014 07:09:23 -0700
Thomas Wouters <thomas at python.org> wrote:
> 
> He means you're being unrealistically pedantic :) The number of calls to
> __eq__ is _already_ unpredictable, since (as Mark Shannon said) it depends
> among other things on the hashing algorithm and the size of the dict.

Well, I was not arguing that the optimization would be an important
compatibility break. Obviously, an __eq__ which would break this
optimization would be particularly dubious (and probably wrong for
other reasons) :-)

Regards

Antoine.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4