Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Python Object-Oriented Python (retired) Inheritance Intro to Inheritance

Patrick Kearns
Patrick Kearns
4,669 Points
Posted by Patrick Kearns
Patrick Kearns
4,669 Points

I'm not fully understanding why we were able to drop the 'kwargs.get()' within the __init__.

From the previous section where we learned about init, it seemed that the power of it relied on 'kwargs.get()'. What is different now that we are able to get the same functionality without it?

1 Answer

Hemanth C
Hemanth C
8,970 Points
Hemanth C
Hemanth C
8,970 Points

looping the kwargs and using the powerful setattr is the replacement those 4 kwargs.get() statements.

self.hit_points = kwargs.get('hit_points', 1)

this is same as setattr(self, 'hit_points', 1)