Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Chris Angelico <rosuav@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: What is a function parameter =[] for?
Date: Thu, 26 Nov 2015 14:02:00 +1100
Lines: 57
Message-ID: <mailman.111.1448506929.20593.python-list@python.org>
References: <d9045bdd-a5d4-4c5c-9fd3-3d54f6b50862@googlegroups.com> <56547337.4000709@rece.vub.ac.be> <CAPTjJmoGt3B_zTVd8dVLHNeanX=4g1yhN-PLpXzZoYiKb9HYuw@mail.gmail.com> <56547C53.8030407@rece.vub.ac.be> <CAPTjJmqAMwnxBZ97umsNg255v47dsQD6qEr0ysECtGiZ409k0Q@mail.gmail.com> <5654864E.2070906@rece.vub.ac.be> <CAPTjJmoUtwHzOEwcObh5hzUDbz-713kVE_Kq-rg_bmYFHE_tYw@mail.gmail.com> <56549324.8020607@rece.vub.ac.be> <CALwzidmAKgmxjR=nDU4bPn5iy9AqCCiT=nTQYSORADCtpdM+SA@mail.gmail.com> <56549F15.40206@rece.vub.ac.be> <CALwzidkuiSfyXxiQ8H6YSEtEL5cqj6sOUPXdUru6n8XtGnvzug@mail.gmail.com> <5654B037.6020107@rece.vub.ac.be> <CALwzidkRj7G-W3UdtdczM10kHmHZ_qrdOoPNcJNjiw2QcNr0YQ@mail.gmail.com> <mailman.33.1448398558.20593.python-list@python.org> <n32jqq$k4j$1@dont-email.me> <mailman.35.1448400323.20593.python-list@python.org> <56550273$0$1585$c3e8da3$5496439d@news.astraweb.com> <mailman.64.1448445391.20593.python-list@python.org> <5655f27b$0$1614$c3e8da3$5496439d@news.astraweb.com> <w2dh9k9bjhq.fsf@daphne.csail.mit.edu> <CAPTjJmqrEhMR7Uq_V1zPUw6huPjKYPMPDciHvJoCwZDXaSkZfg@mail.gmail.com> <CALwzidmFqTWodNxGnJSoeV3wWMvi8dP-6X=dp_kT8m6r=WLcog@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
In-Reply-To: <CALwzidmFqTWodNxGnJSoeV3wWMvi8dP-6X=dp_kT8m6r=WLcog@mail.gmail.com>
Precedence: list
Xref: csiph.com comp.lang.python:99524

On Thu, Nov 26, 2015 at 1:46 PM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Wed, Nov 25, 2015 at 7:25 PM, Chris Angelico <rosuav@gmail.com> wrote:
>> On Thu, Nov 26, 2015 at 1:08 PM, Alan Bawden <alan@csail.mit.edu> wrote:
>>> (Note that nothing in the documentation I can find actually _guarantees_
>>> that a Python implementation will only have one unique empty tuple, but
>>> I wouldn't be suprised if the following is nonetheless true in all
>>> current implementations:
>>>
>>>    >>> tuple([]) is tuple([])
>>>    True
>>>
>>> )
>>
>> Jython 2.5.3 (, Oct 8 2014, 03:39:09)
>> [OpenJDK 64-Bit Server VM (Oracle Corporation)] on java1.7.0_85
>> Type "help", "copyright", "credits" or "license" for more information.
>>>>> tuple([]) is tuple([])
>> False
>>
>> Python 2.7.8 (2.4.0+dfsg-3, Dec 20 2014, 13:30:46)
>> [PyPy 2.4.0 with GCC 4.9.2] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> tuple([]) is tuple([])
>> False
>
> Well, he did say all "current" implementations. CPython 2.7 may still
> be supported, but that doesn't make it current. And anything at 2.5 is
> just archaic.

Those are the versions of Jython and PyPy available from the Debian
Jessie repositories. I'm not sure what Jython's compatibility is, but
this is at least reasonably current.

But I grabbed the latest 2.x-compatible PyPy nightly:

Python 2.7.10 (b4515dee6ebf, Nov 25 2015, 23:01:41)
[PyPy 4.1.0-alpha0 with GCC 4.8.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``Every time someone argues with
"Smalltalk has always done X", it is always a good hint that something needs to
be changed fast. - Marcus Denker''
>>>> tuple([]) is tuple([])
False

The latest PyPy3 nightly builds seem to be broken, though; I was
unable to get one to run. The builds compatible with Python 3.2 work,
though:

Python 3.2.5 (b2091e973da6, Oct 19 2014, 18:29:55)
[PyPy 2.4.0 with GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>> tuple([]) is tuple([])
False

So current PyPy still behaves that way.

ChrisA