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/2018-June/153975.html below:

[Python-Dev] About [].append == [].append

[Python-Dev] About [].append == [].append [Python-Dev] About [].append == [].appendSerhiy Storchaka storchaka at gmail.com
Fri Jun 22 01:00:13 EDT 2018
22.06.18 00:04, Ivan Pozdeev via Python-Dev пише:
> On 21.06.2018 23:40, Guido van Rossum wrote:
>> I'm with Serhiy here, for mutable values I don't think the methods 
>> should compare equal, even when the values do. For immutables I don't 
>> care either way, it's an implementation detail.
>>
> In this light, methods rather shouldn't have a rich comparison logic at 
> all

This would be so if you get the same method object when resolve an 
attribute. But a.f is not a.f. Every time a new method object is 
created. If we want a.f == a.f, we need to implement a rich comparison 
logic.

> -- at the very least, until we have a realistic use case and can 
> flesh out the requirements for it.

There are realistic use cases. You will get a number of failures in the 
Python tests if make method objects incomparable.

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