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/2004-March/043193.html below:

[Python-Dev] A proposal has surfaced on comp.lang.pythontoredefine "is"

[Python-Dev] A proposal has surfaced on comp.lang.pythontoredefine "is" [Python-Dev] A proposal has surfaced on comp.lang.pythontoredefine "is"Andrew Koenig ark-mlist at att.net
Wed Mar 17 20:08:14 EST 2004
> Ah, but that would be definite incompatible change in semantics.  I
> would be very suprised if this printed "IS":
> 
> a = []
> b = []
> if (a, b) is (a, b): print "IS"
> else: print "ISN'T"

Indeed, it would be a change.  And I can go along with an argument that an
incompatible change of that magnitude should be rejected for that reason
alone.  But why would the change cause a problem?  Consider:

	a = []
	b = []
	x = (a, b)
	y = (a, b)

Can you think of a program that can make productive use of the value of
"x is y"?  It seems to me that x and y are mutually substitutable.


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