boards.py

Hi Jonathan,

I agree with your statement the init in a subclass has to have at least all the same values as it's parent class, plus whatever new arguments are going into the subclass. The subclass must pass the super's requirements inside the super().__init__ call. But that doesn't mean these values need to be passed to the subclass init method. The subclass can just send values as I have done - these don't have to be hard-coded as above - they can be calculated from other aspects of the class. But as long as super gets its required parameters pass in, it'll be happy. For situations like this, where the Board size within the subclass is best not exposed to the user's error-risk, this way of approaching it is way safer!

I don't recall that particular part of this course re the Sneaky call to super - can you point me to it (they're also on the Linux partition of this machine; I've booted into Windows at the moment!)? You are right that those calls to super() will end with the Object class to handle as generic classes like Sneaky and Agile have Object as their superclass.

Point me to the right part of the course and I'll have a look for you.

Steve.

You rock Steve! Lots of clarity :)

thanks for the quick response! I've watched/read a few different videos/articles covering init and super().init, and I haven't seen anyone do what you just did in the above code. So far from what I've taken in, the init in a subclass has to have at least all the same values as it's parent class, plus whatever new arguments are going into the subclass, and then the super().init goes looking for the O.G. variables you want the parent class to take care of. Seeing you write that above is a little bit mind blowing. "I CAN DO THAT?!!?" This makes creating subclasses seem way easier and more flexible. I suppose I can blame myself for not experimenting more and figuring it out on my own, but it just seemed like the way I learned was the RULE.

I have another question about super() if you have time to answer it.

import random


class Sneaky:
    sneaky = True

    def __init__(self, sneaky=True, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.sneaky = sneaky

    def hide(self, light_level):
        return self.sneaky and light_level < 10


class Agile:
    agile = True

    def __init__(self, agile=True, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.agile = agile

    def evade(self):

This is the code under agile.py that Kenneth wrote in the object oriented workspace. Why did he put super()init in these classes? They're not subclasses of anything right? (except of course the python object class that all objects are under) From my understanding of super(), it goes to the parent class to look for whatever arguments listed within it. If you don't have time to answer that I understand, and I'll keep looking on my own.

Thanks again!

https://teamtreehouse.com/library/multiple-superclasses I'm not sure if it will come up for you, but under this video if I launch workspaces, and launch the workspace Kenneth set up for this part of the class, it will contain the file attributes.py, which is what I posted up there (sneaky, etc) Thank you again sooo much for responding with all this detail, I really appreciate it.