When I first discovered the walrus operator (:=), I thought:
“It’s just syntactic sugar.”
After all, you can write the same code without it.
So why does it exist?
What does the walrus operator do?
The walrus operator lets you assign a value while evaluating an expression.
Instead of this:
match = pattern.match(line)
if match:
print(match.group())
You can write:
if (match := pattern.match(line)):
print(match.group())
You both assign and check the value in one place.
Where it actually shines
One of my favorite use cases is list comprehensions.
import re
pattern = re.compile(r"ERROR (\d+): (.*)")
errors = [
(int(m.group(1)), m.group(2))
for line in log_lines
if (m := pattern.match(line))
]
Without :=, you’d either need an extra loop or call pattern.match() twice.
Another practical example is guard clauses.
if (result := a * b) > 10:
raise ValueError(
f"Result ({result}) is too large."
)
Here, the value is calculated only once and can be reused in the error message.
Should you use it everywhere?
Probably not.
The walrus operator improves code only when it makes the logic easier to follow.
If it makes a line harder to read, a separate assignment is usually the better choice.
Like many Python features, it’s a tool—not a rule.
Final thoughts
At first glance, the walrus operator looks unnecessary.
But in the right situations, it reduces repetition, avoids duplicate calculations, and keeps related logic together.
The key is using it intentionally, not everywhere.
What’s your opinion?
Do you use the walrus operator in your projects, or do you prefer traditional assignments?
Top comments (1)
I think the biggest benefit of the walrus operator isn’t saving a line of code—it’s making the evaluation explicit and avoiding duplicated work.
For inexpensive expressions the difference is mostly stylistic, but when the expression is expensive, has side effects, or returns a value you immediately need again (like regex matches or parsing), := keeps the intent clear while ensuring it only runs once.
Like any language feature, readability should be the deciding factor. If the walrus makes the code harder to understand, I’d rather keep the assignment on its own line.