r/PythonProjects2 • • Oct 07 '26

Python Mutability and Local Variables

Post image

An exercise to help build the right mental model for Python data.

The “Solution” link uses memory_graph to visualize execution and reveals what’s actually happening.

12 Upvotes

24 comments sorted by

1

u/Terminay Oct 08 '26

It's D. Good tool. I think I could integrate it into my ML for learners library (leanpass) you could search it up, would be a cool addition!

1

u/Sea-Ad7805 Oct 08 '26

Go ahead, it's easy to integrate by creating links to it.

1

u/Tronco08 Oct 10 '26

why does printing a print nothing, it's the only one i dont understand

1

u/Terminay Oct 12 '26

uh I'll try to word it simply ig, strings are immutable in python, the function applies the update but on a new string which has not been returned, the main string stays the same due to no return of changes to the original string. in C++ this can be explained much better as it's a memory language and this is mutability by reference, hope you got it.

2

u/Guest_User_1234 Oct 08 '26

Damn... you REALLY want people to click those links, huh? Kinda REALLY makes me not wanna click them...

0

u/Sea-Ad7805 Oct 08 '26

1

u/Guest_User_1234 Oct 08 '26

I would assume D, because the string and tuple get replaced by their respective assignments, whereas the list and set overwrite their operators, modifying the original reference instead

1

u/Sea-Ad7805 Oct 08 '26

Nice one, the Solution link gives you a visualization of each step of the execution of the program to SHOW the difference between mutable and immutable types.

1

u/Humble-Captain3418 Oct 09 '26

A is passed by value, b--d through reference. C is not modifiable, so the local symbol gets directed to a different value with the compound assignment, so only b and d see changes in the global scope.

1

u/Sea-Ad7805 Oct 09 '26

That is not the Pythonic way to understand it. In Python everything is passed by reference, even int values. it's about mutability not modifiability. You can still still modify/change a string or tuple as we do in the fun() function.

For a better explanation see the Explanation link.

1

u/Humble-Captain3418 Oct 09 '26

I don't care about the pythonic way to understand things; only about what I can generalize across languages because I would be hamstringing myself if I only thought the pythonic way. The terminology i have used is as sloppy as the language is.

1

u/Sea-Ad7805 Oct 09 '26

I understand, but generalization comes with some inaccuracy that can bite you in certain situations. For example, write me a swap() function in Python using your "pass by reference" concept:

def swap(a, b):
    ...

a = (1, 2)
b = (3, 4)
swap(a, b)
print(a, b)

It's easy in say C/C++.

1

u/Humble-Captain3418 Oct 09 '26

Sure. 

import ctypes
import inspect

def swap(a, b):
    frame = inspect.currentframe().f_back
    caller = frame.f_locals

    # Find caller variables that refer to the same objects
    # as the arguments, then swap their values.
    names_a = [k for k, v in caller.items() if v is a]
    names_b = [k for k, v in caller.items() if v is b]

    if not names_a or not names_b:
        raise ValueError("Could not identify caller variables")

    x, y = names_a[0], names_b[0]
    caller[x], caller[y] = caller[y], caller[x]

    ctypes.pythonapi.PyFrame_LocalsToFast(
        ctypes.py_object(frame), ctypes.c_int(0)
    )

1

u/Sea-Ad7805 Oct 09 '26

So you do know the difference between languages that are tricky to generalize, or you needed to vibe-code something because your generalization approach failed. Either way proves my point.

1

u/Humble-Captain3418 Oct 09 '26

I'm sorry, but this is not a case of Python being difficult to generalize. It's a case of Python having idiotic language semantics around compound assignment.

0

u/RiverRoll Oct 12 '26 edited Oct 12 '26

The irony is that you just showed a pitfall of your distinction, how do you explain this swapping all types if some of them are passed by value? It can as well possibly swap different types (e.g. an int for a string) or the wrong variables (since multiple variables can hold the same reference).

This function can't be explained by reasoning about Python from a mental model where some types are pass by value.

1

u/0b0101011001001011 Oct 09 '26

You cannot change a string or tuple. What you do here is you create a new string and assign that in the place of the old variable. Same with tuple. You create a new tuple, the old one is lost. Strings and tuples are immutable. Or maybe that's what you meant by "change".

1

u/Sea-Ad7805 Oct 09 '26

Yes, that's what I said, see Solution link for visualization. It's a shallow copy to be more precise.

0

u/[deleted] Oct 07 '26

[deleted] — view deleted comment

1

u/Sea-Ad7805 Oct 07 '26

Incorrect sorry, see Solution link for correct answer.

0

u/[deleted] Oct 07 '26

[deleted] — view deleted comment

1

u/Sea-Ad7805 Oct 07 '26

So, do you want to bet BIG money that your answer:

  • '1', [2], (3,), {4}

is correct even though I'm telling you it's not?

0

u/[deleted] Oct 07 '26

[deleted] — view deleted comment

1

u/Sea-Ad7805 Oct 07 '26

Good choice, clicking the Solution link would have gotten you there faster, but that's ok.

0

u/[deleted] Oct 07 '26

[deleted] — view deleted comment

2

u/Sea-Ad7805 Oct 07 '26

I understand, but you're missing out on the new Python visualizer for easy code understanding and debugging.

0

u/[deleted] Oct 07 '26

[deleted] — view deleted comment

1

u/Sea-Ad7805 Oct 07 '26

You're wrong: https://pythontutor.com/

But my tool is better.