r/learnpython • u/codehorsey Github codehorsey • Aug 14 '17
I finally understand classes thanks to this presentation.
As a newbie to coding in general and having trouble understanding classes. This helped me a bunch, I hope others can find it useful.
12
u/Aiognim Aug 14 '17
I really enjoyed the break down and the size of the slides. I could learn a great deal that way.
Props to the author.
Thanks for sharing.
4
u/LeonardFibonacci Aug 14 '17
That was a fantastic presentation! Iām new to python and this cleared a few things up for me. Thank you.
2
u/pookeye Aug 15 '17
this is a great presentation, im still very new to classes, but this helps a lot.
2
u/Thecrawsome Aug 15 '17
I shy away from OOP in-general with Python, personally.
If I need OOP, it's C++. There's a little extra boilerplate, but man, Python is not ideal for OOP. It's too expensive.
2
u/Freezingcow Aug 15 '17
I wish all elements of programming was explained this way. Explaining things with analogy is hands down the best way to teach and learn in my honest opinion. One of my teachers back in the day did this all the time and I've never been more excited than when I went to his classes.
1
1
1
1
u/0k4n3n4s 0kanenas at Github Aug 14 '17
Man that was useful! Thanks for sharing!! āššØāš»
0
Aug 14 '17
[deleted]
2
u/codehorsey Github codehorsey Aug 15 '17
Thanks, I had to share it. Cleared everything up for me :)
53
u/filletrall Aug 14 '17
I want to point out a small (very small) problem with this tutorial:
Here, there's a class attribute named fish, and then there's an instance attribute named fish. The class attribute is never used, because it's being hidden (shadowed) by the instance attribute. You can still get at it:
But it's unneeded, since aquariums in general don't share fish between them. Each instance has fish, independent of any other instance.
It's also confusing for newbies, who might get the idea that all instance attributes needs a shadow class attribute, or that it's a good idea to use class attributes as a sort of "default value". Instead, simply drop the second line:
It's best to only use class attributes to store attributes that describe or otherwise truly belong to the class, and not each instance.
There are definitely cases where putting a list or a dict on the class object makes sense, typically when you wish to track some aggregate property of all the instances, like a sum or a list of the instances. To avoid unintended behavior and make it clear what the intention of the code is, always access class attributes directly on the class object, and not through self: