At first word Metaprogramming seems very funky and alien thing but if you have ever worked with decorators or metaclasses, your were doing metaprogramming there. In nutshell we can say metaprogramming is the code which manipulates code.
In this article we are going to discuss about Metaclasses, why and when we should use them and what are the alternatives. This is fairly advance Python topic and following prequisite is expected –
- OOP concept in Python
- Decorators in Python
Note: This article considers Python 3.3 and above
In Python everything have some type associated with it. For example if we have a variable having integer value then it’s type is int. You can get type of anything using type() function.
Type of num is: <class 'int'> Type of lst is: <class 'list'> Type of name is: <class 'str'>
Every type in Python is defined by Class. So in above example, unlike C or Java where int, char, float are primary data types, in Python they are object of int class or str class. So we can make a new type by creating a class of that type. For example we can create a new type Student by creating Student class.
Type of stu_obj is: <class '__main__.Student'>
A Class is also an object, and just like any other object it’s a instance of something called Metaclass. A special class type creates these Class object. The type class is default metaclass which is responsible for making classes. For example in above example if we try to find out the type of Student class, it comes out to be a type.
Type of Student class is: <class 'type'>
Because Classes are also an object, they can be modified in same way. We can add or subtract fields or methods in class in same way we did with other objects. For example –
This whole meta thing can be summarized as – Metaclass create Classes and Classes creates objects
Metaclass is responsible for generation of classes, so we can write our own custom metaclasses to modify the way classes are generated by performing extra actions or injecting code. Usually we do not need custom metaclasses but sometime it’s necessary.
There are problems for which metaclass and non-metaclass based solutions are available (often simpler) but in some cases only metaclass can solve the problem. We will discuss such problem in this article.
Creating custom Metaclass
To create our custom metaclass, our custom metaclass have to inherit type metaclass and usually override –
- __new__(): It’s a method which is called before __init__(). It creates the object and return it. We can overide this method to control how the objects are created.
- __init__(): This method just initialize the created object passed as parameter
We can create classes using type() function directly. It can be called in following ways –
- When called with only one argument, it returns the type. We have seen it before in above examples.
- When called with three parameters, it creates a class. Following arguments are passed to it –
- Class name
- Tuple having base classes inherited by class
- Class Dictionary: It serves as local namespace for the class, populated with class methods and variables
Consider this example –
Type of Test class: <class 'type'> Type of test_obj: <class '__main__.Test'> This is inherited method! This is Test class method! atul
Now let’s create a metaclass without using type() directly. In the following example we will be creating a metaclass MultiBases which will check if class being created have inherited from more than one base classes. If so, it will raise an error.
Traceback (most recent call last): File "<stdin>", line 2, in <module> File "<stdin>", line 8, in __new__ TypeError: Inherited multiple base classes!!!
Solving problem with metaclass
There are some problems which can be solved by decorators (easily) as well as by metaclasses. But there are few problems whose result can only be achived by metaclasses. For example consider a very simple problem of code repetition.
We want to debug class methods, what we want is that whenever class method executes, it should print it’s fully qualified name before executing it’s body.
Very first solution that comes in our mind is using method decorators, following is the sample code –
Full name of this method: Calc.add 5 Full name of this method: Calc.mul 10
This solution works fine but there is one problem, what if we want to apply this method decorator to all subclasses which inherit this Calc class. In that case we have to separately apply method decorator to every subclass just like we did with Calc class.
The problem is if we have many such subclasses, then in that case we won’t like adding decorator to each one separately. If we know beforehand that every subclass must have this debug property, then we should look up to metaclass based solution.
Have a look at this metaclass based solution, the idea is that classes will be created normally and then immediately wrapped up by debug method decorator –
Full name of this method: Calc_adv.mul 6
When to use Metaclasses
Most of the time we are not using metaclasses, they are like black magic and usually for something complicated, but few cases where we use metaclasses are –
- As we have seen in above example, metaclasses propogate down the inheritence hierarchies. It will affect all the subclasses as well. If we have such situation, then we should use metaclasses.
- If we want to change class automatically, when it is created
- If you are API developer, you might use metaclasses
As quoted by Tim Peters
Metaclasses are deeper magic that 99% of users should never worry about. If you wonder whether you need them, you don’t (the people who actually need them know with certainty that they need them, and don’t need an explanation about why).
Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.