languages/what-a-variable-really-is-python-names-values-and-the-sign.md
What a variable really is: Python names, values and the = sign
In Python, a variable isn't a box that holds a value. It's a name tag tied to a value that lives on its own.
That one picture explains why age = age + 1 makes perfect sense, why = is an instruction rather than a statement of fact, and why changing a list through one name can quietly change it under another name too.
Step through two tiny programs and watch the names and values move, test your own variable names against Python's rules, then finish with a four-question check.
$ ls languages/
see all →
languages/javascript-closures-how-a-function-remembers-a-variable-after-the-func.md
JavaScript closures: how a function remembers a variable after the function that made it has finished
A function in JavaScript can still use a variable long after the function that created it has finished. That is called a closure, and you…
languages/ruby-blocks-how-a-method-borrows-a-piece-of-your-code-and-runs-it-with.md
Ruby blocks: how a method borrows a piece of your code and runs it with yield
Ruby code is full of curly-brace chunks like `list.each { |x| ... }`. Who runs that chunk, and when? This article follows a block from the…
languages/reference-counting-how-python-knows-when-to-throw-an-object-away.md
Reference counting: how Python knows when to throw an object away
You never tell Python to free memory, yet unused objects disappear. How does it know when one is finished with? CPython keeps a tally on…
languages/generators-how-a-python-function-can-pause-in-the-middle-and-pick-up-w.md
Generators: how a Python function can pause in the middle and pick up where it left off
A generator is a Python function that can pause halfway, hand you a value, and carry on later from the same line with its variables intact…
languages/javascript-s-event-loop-why-settimeout-0-runs-after-the-code-below-it.md
JavaScript's event loop: why setTimeout(…, 0) runs after the code below it
Why does `setTimeout(fn, 0)` run after the lines below it, and why does a promise callback beat it? JavaScript has one worker and two…
languages/rust-ownership-why-let-b-a-makes-a-unusable.md
Rust ownership: why let b = a makes a unusable
Why does Rust refuse to compile `let b = a;` followed by a use of `a`? Because of ownership: every value has exactly one owner, and…