13 ms·
With regard to "pass by reference", it's not even clear to me that that's a correct way to describe how Python passes variables to functions. Python variables a
by pdonis 8y ago
With regard to "pass by reference", it's not even clear to me that that's a correct way to describe how Python passes variables to functions. Python variables aren't names for storage locations to begin with; they're namespace bindings. Passing a variable to a function means passing a particular namespace binding from the caller's namespace to the function's local namespace. I don't think the author of this article understands any of that.
- tom_mellior 8y ago> Python variables aren't names for storage locations to begin with; they're namespace bindings. Can you explain the difference? What is a "namespace binding"? When accessing a variable's value, the interpreter's code sure looks like it treats the variable name as the name of a storage location. > Passing a variable to a function means passing a particular namespace binding "Passing a variable to a function" is not a thing. Passing a value to a function means passing a pointer to that value. This is the same for "foo(some_var)" and "foo(1)". Since "1" is presumably not a "namespace binding", you seem to suggest that there are different parameter passing mechanisms for these cases. There aren't.
- kzrdude 8y agoEvery value in Python is a reference to an object. All function parameters are such values that are passed as they are. You get the same references to objects that the caller passed. We could call this "passing references to objects by value."
- zephyrfalcon 8y agoOver the years, I have found this article to be useful: http://effbot.org/zone/call-by-object.htm http://effbot.org/zone/call-by-object.htm
- Izkata 8y agoThat's a long form of what I most often hear: "pass by value of reference" But in any case, that's the point that made me go wtf while reading through as well. Whatever you want to call it, it's the same as what C (when not passing pointers), Java, PHP, Javascript, and many many other languages use. Which is why it's so frustrating we don't have a good, easily-understood/well-known name for it.
- d0mine 8y agoHere are pictures that explain the difference between variables as named boxes and names in Python https://david.goodger.org/projects/pycon/2007/idiomatic/handout.html#other-languages-have-variables https://david.goodger.org/projects/pycon/2007/idiomatic/hand...
- tom_mellior 8y agoThat's a nice explanation for BASIC programmers, but for anyone who has ever programmed in some other programming language than BASIC, it should not come as a surprise that named boxes can store pointer values. As they do in Python. They literally store C pointers of type (PyObject *).
- d0mine 8y agoPython is not C. There are no pointers in Python. I have no idea why would you mention BASIC here.
- pdonis 8y ago> What is a "namespace binding"? An entry in a Python dictionary that is the namespace for the current scope. For example, to repeat a response I gave to someone else upthread, compare a variable assignment in C and Python. In C: int i = 17; Means "set aside one int's worth of storage and fill it with the bit pattern for the number 17". In Python: i = 17 means "create an int object with the value 17 and bind it in the current namespace dictionary to the name i".
- tom_mellior 8y agoIn other words, the latter means "set aside one pointer's worth of storage and fill it with the bit pattern for the pointer pointing to the value 17 (which you may have to create first)". Variables have values. In C those values may be ints, floats, pointers, whatnot. In Python (at the implementation level) those values are pointers to objects.
- pdonis 8y ago> In other words, the latter means "set aside one pointer's worth of storage Set aside one pointer's worth of storage on the heap, yes; not on the stack or in the program's data segment, which is what the C statement I gave does. > and fill it with the bit pattern for the pointer pointing to the value 17 (which you may have to create first)" Which has no analogue whatever in the C version. Also, you completely left out the part about creating an entry in the namespace dictionary, which also has no analogue whatever in the C version, and which involves additional memory allocations.
- tom_mellior 8y ago> not on the stack Except for locals. (Well, OK, the Python stack is reified in the heap, but local variables are translated into small integer indices into the stack frame.) > an entry in the namespace dictionary Except for locals, which do not involve memory allocations or dictionary lookups. Anyway, we're getting farther and farther away from the topic, which was that Python argument passing is no different from any other language in which everything is an object.
- pstch 8y ago> Passing a variable to a function means passing a particular namespace binding from the caller's namespace to the function's local namespace. I don't think that's true, as the function will never be able to change the binding, and only gets a reference to the value of the binding. If the function was passed a particular namespace binding, it would be able to change this binding's value, and that's not possible. I agree that "pass by reference" is a misleading way to describe Python functions.
- pdonis 8y ago> the function will never be able to change the binding, and only gets a reference to the value of the binding More precisely, the function's arguments when it is called are a set of values for variables taken from the caller's namespace, which then get bound to the corresponding names in the local namespace. You're right that "passing the binding" doesn't really describe that process very well.
- tom_mellior 8y ago> the function's arguments when it is called are a set of values for variables taken from the caller's namespace Again, this is very obviously false, since a call need not involve any variables at all: foo(1, 2, "three") The function's arguments when it is called are a set of values taken from the caller, yes. And those values are obtained from evaluating expressions that may involve variables. But they might not. Saying that the values are "a set of values for variables taken from the caller's namespace" is wrong. You are mistaken, and your talk of namespace bindings is just obfuscation. Python arguments are passed by pointer. Python namespaces bind names to pointers. There is no "binding" object passed in a function call.
- pdonis 8y ago> this is very obviously false, since a call need not involve any variables at all True, in which case the values would just be constants. But they will still get bound to names in the function's local namespace. > You are mistaken No, I left out a case which, it seemed to me, did not affect the main point I was making. If you want to make clear that that's a possible case, fine, you've done so. But you haven't refuted (or even engaged with) my main point at all. > your talk of namespace bindings is just obfuscation No, it's a very important difference between what Python variables mean and what variables in language like C mean. You might think the difference is unimportant, but not everyone agrees with you. > Python arguments are passed by pointer. Python namespaces bind names to pointers. At the C level inside the interpreter, yes, this is true: every "object", such as the 1, 2, and "three" in your example, is a pointer to a C struct containing the object's data (sometimes including further pointers). Again, that doesn't affect my main point at all. > There is no "binding" object passed in a function call. I already agreed to this in my response to pstch upthread (the post of mine you originally replied to). Once more, it doesn't affect my main point at all.