Python Learning
Kanalga Telegramāda oātish
Python learning resources Beginner to advanced Python guides, cheatsheets, books and projects. For data science, backend and automation. Join š https://rebrand.ly/bigdatachannels DMCA: @disclosure_bds Contact: @mldatascientist
Ko'proq ko'rsatish5 787
Obunachilar
-324 soatlar
-327 kunlar
-5530 kunlar
Postlar arxiv
5 788
+1
Wait, why did all functions return 2?
The lambdas donāt capture the value of
i at each loop iteration, they capture the variable itself. By the time you call the functions, the loop has finished, and i is left at its final value, 2.
This is called late binding and can cause unexpected behavior when creating closures inside loops.
So as a quick tip, Bind the current value at definition time using a default argument(like shown in the second image) Then each lambda remembers its own i value independently.5 788
Feels off?
It's because all your objects share one variable (without you realizing it)
At first glance, it seems like every object should start fresh, right? But in this case, count is a class variable, which means itās shared by all instances of the class.
Every time you create a new
Counter(), youāre actually incrementing the same shared variable not something unique to each object.
If your goal is to give each object its own value, define it like this instead
class Counter:
def __init__(self):
self.count = 1
Now, each instance has its own count, stored on the object itself . no sharing, no surprises.5 788
Looks weird? You're not alone.
Python caches small integers between -5 and 256 for performance. So a and b point to the same object. But x and y are different objects, even though they have the same value.
This is part of Python's internal optimization. Itās not about math. itās about memory references under the hood.
Bottom Line?
Use == when you care about value, not identity.
print(x == y) # True ā
Because sometimes is isnāt what you think it is š