Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Mark H Harris <harrismh777@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: immutable vs mutable
Date: Tue, 03 Jun 2014 15:35:45 -0500
Organization: Aioe.org NNTP Server
Lines: 18
Message-ID: <lmlbit$rds$1@speranza.aioe.org>
References: <mailman.10641.1401824651.18130.python-list@python.org>
NNTP-Posting-Host: eSF12mcVRIwL+eMIMJ03mA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.python:72545

On 6/3/14 12:29 PM, Deb Wyatt wrote:

>
> http://www.spontaneoussymmetry.com/blog/archives/438
>
> Deb in WA, USA

The article is bogged down in unnecessary complications with regard to 
mutability (or not) and pass-by reference|value stuff. The author risks 
confusing her audience (those who are perhaps already confused about the 
nature of variables in Python).

The examples deal mostly with names and scope. The article in my opinion 
confuses a Python concept which is otherwise very straight-forward which 
has been beat to death on this forum.

marcus