On 05/10/2014 02:05 AM, Rustom Mody wrote:
On Saturday, May 10, 2014 1:18:27 PM UTC+5:30, Steven D'Aprano wrote:
Python assignment doesn't copy values.
Maybe our values differ?
Obviously they do. Yours are irrelevant for Python. They could be, and probably are, useful when comparing and
On Sat, 10 May 2014 11:18:59 +0300, Marko Rauhamaa wrote:
> In Python,
>
>x is a variable, a memory slot that can be assigned to,
If your intention was to prove Ben Finney right, then you've done a
masterful job of it. Python variables ARE NOT MEMORY SLOTS.
(Not even local variables
On Saturday, May 10, 2014 1:18:27 PM UTC+5:30, Steven D'Aprano wrote:
> Python assignment doesn't copy values.
Maybe our values differ ?
--
https://mail.python.org/mailman/listinfo/python-list
Chris Angelico :
> On Sat, May 10, 2014 at 5:48 PM, Steven D'Aprano
> wrote:
>>> https://en.wikipedia.org/wiki/Assignment_(computer_science)
>>>
>>> Go ahead, start an edit war at that page over its use of "variable". :)
>>> Right there it talks about copying values into variables. So if Python
>
Chris Angelico :
> On Sat, May 10, 2014 at 3:58 PM, Gregory Ewing
> wrote:
>> Steven D'Aprano wrote:
>>>
>>> some_function(x, y+1)[key].attribute[num](arg)[spam or eggs] = 42
>>>
>>> I'm pretty sure that it isn't common to call the LHS of that assignment a
>>> variable.
>
> [...]
> https://en.wik
On Sat, May 10, 2014 at 5:48 PM, Steven D'Aprano
wrote:
>> https://en.wikipedia.org/wiki/Assignment_(computer_science)
>>
>> Go ahead, start an edit war at that page over its use of "variable". :)
>> Right there it talks about copying values into variables. So if Python
>> has no variables, then e
On Sat, 10 May 2014 17:10:29 +1000, Chris Angelico wrote:
> On Sat, May 10, 2014 at 3:58 PM, Gregory Ewing
> wrote:
>> Steven D'Aprano wrote:
>>>
>>> some_function(x, y+1)[key].attribute[num](arg)[spam or eggs] = 42
>>>
>>> I'm pretty sure that it isn't common to call the LHS of that
>>> assignme
On Sat, May 10, 2014 at 3:58 PM, Gregory Ewing
wrote:
> Steven D'Aprano wrote:
>>
>> some_function(x, y+1)[key].attribute[num](arg)[spam or eggs] = 42
>>
>> I'm pretty sure that it isn't common to call the LHS of that assignment a
>> variable.
>
>
> A better way of putting it might be "something i
Steven D'Aprano wrote:
some_function(x, y+1)[key].attribute[num](arg)[spam or eggs] = 42
I'm pretty sure that it isn't common to call the LHS of that assignment a
variable.
A better way of putting it might be "something in the data
model that can be assigned to".
--
Greg
--
https://mail.pyth
On 5/9/14 8:34 PM, Steven D'Aprano wrote:
Nobody seems to complain about using the term "assigment" in relation to
Python, despite it meaning something a bit different from what it means
in some other languages, so I don't see anything wrong with using the
term "variable" with the above definitio
On Fri, 09 May 2014 13:10:41 +1200, Gregory Ewing wrote:
> Steven D'Aprano wrote:
>> Today we routinely call horseless carriages "cars", and nobody would
>> blink if I pointed at a Prius or a Ford Explorer and said "that's not a
>> carriage, it's a car" except to wonder why on earth I thought some
Gregory Ewing writes:
> If you look at the way the word "variable" is used across a variety of
> language communities, the common meaning is more or less "something
> that can appear on the left hand side of an assignment statement".
The clear experience from years in this and other Python forum
Steven D'Aprano wrote:
Today we routinely call horseless carriages
"cars", and nobody would blink if I pointed at a Prius or a Ford Explorer
and said "that's not a carriage, it's a car" except to wonder why on
earth I thought something so obvious needed to be said.
That's only because the ter
13 matches
Mail list logo
