FAQ: Object-Oriented Programming - OOP Pillar: Abstraction

This community-built FAQ covers the “OOP Pillar: Abstraction” exercise from the lesson “Object-Oriented Programming”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn Intermediate Python 3

FAQs on the exercise OOP Pillar: Abstraction

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!
You can also find further discussion and get answers to your questions over in Language Help.

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head to Language Help and Tips and Resources. If you are wanting feedback or inspiration for a project, check out Projects.

Looking for motivation to keep learning? Join our wider discussions in Community

Learn more about how to use this guide.

Found a bug? Report it online, or post in Bug Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

So, what’s the point of adding an abstract method to the Animal class? Wouldn’t the Cat class throw an error if I called make_noise() and hadn’t defined it there whether the Animal class had the abstract method or not?


I think this pillar is very important, and the narrative just distracts the important points to get from this pillar.

I’m curious about this to. I commented out the @abstractmethod and ran the program with the say_id() in the childclass and it ran just fine. I’m still not sure why I would use the @abstractmethod and not just delete it from the parentclass.

1 Like

I am confused as well. I see no point in it and it changes nothing when I just comment it all out in the abstract class. Came to this forum hoping to find an answer but unfortunately there isn’t one.

I don’t think that the whole explanation makes a point. Also I agree that narrative confuses and distracts, like “The .__init__() method still requires a name, since we feel all animals deserve a name.”

An explanation of decorator (@abstractmethod) is clearly explained here: https://blog.teclado.com/python-abc-abstract-base-classes/


@kimsergeo posted a good link that provides some light on this. From what I can tell, the @abstractmethod decorator allows you to organize your classes by declaring the methods that you want to be apart of the AbstractEmployee subclasses.

If you try to make a method called ‘print_id’ instead of ‘say_id’ within the Employee class it will give you an error. The @abstractmethod allows us to set the name of the methods that we want all of our subclasses to have.

I agree with what has bee said before, this particular lesson could do with a bit more clarity - it is confusing, I needed to do some extra reading outside of codecademy to really understand.