Python supports object-oriented programming capabilities and very soon you will begin to encounter the need to explore and adapt these capabilities for use in your program. Like in other OOP languages, a class in Python can be viewed as a recipe for creating objects of that class.
For instance, let us create a class to denote “cash registers”. A cash register has a make (a string), a year of manufacture (an integer), and a balance (a floating point number). We can encapsulate these variables into a class like so:
In the above program the CashRegister class has make, year, and bal (balance) attributes. In the last two lines we define two cash registers, called cr1 and cr2. cr1 is an Olivetti cash register manufactured in 2010 with a balance of $0. cr2 is a Honeywell cash register manufactured in 2022 and also set with a balance of $0.
We can write some useful methods for cash registers within the above class definition:
ring_purchase merely rings a purchase: it takes the cost of an item and adds it to the balance.
If we now try:
The output will be:
We can also attempt to print a cash register as a whole:
This will give some output such as:
(your specific results might vary). This is because Python has not been told how to print cash register objects. Let us write a Python method for this purpose:
Now if we try:
You will still get the same output as before. This is because this print() is the same default system print() of Python. Instead you must do:
Now you will get:
Now you might argue that cash registers do not exist by themselves in the middle of a highway. They are usually found in stores or restaurants. So we might choose to create a class called “Restaurant” and nest the CashRegister class within that class.
Here is how that might work:
Nesting Python classes
In the below code, we create a Restaurant class and completely nest all the code we have written thus far for cash registers inside this class, like so:
Note that the class Restaurant in its constructor has a name, an address, and a default cash register (which is setup to be a Honeywell cash register manufactured in 2021 with a balance of zero). We can access the inner class (ie CashRegister) in the outer class (ie Restaurant) using the self keyword.
We can now setup a restaurant like so:
We now have a McDonalds’ restaurant on 123 Main Street and inside this restaurant we know that it has a Honeywell cash register manufactured in 2021.
If we now try:
What is the big deal? We could do these same things before nesting the class. The fine print is in what you are NOT allowed to do anymore. For instance, let us try creating a cash register like before:
We will get an error like:
because CashRegister is nested inside the Restaurant class, we cannot access it directly. We can only access it “through” the Restaurant class.
When should you nest classes in Python?
You should nest classes when you have related concepts (like Restaurant and CashRegister) and you desire to not make the inner class accessible without the context of the outer classes. This also helps in information hiding and improved program comprehension.
Kodeclik is an online coding academy for kids and teens to learn real world programming. Kids are introduced to coding in a fun and exciting way and are challeged to higher levels with engaging, high quality content.