Home > Article > Backend Development > How to define multiple constructor method overloading and generic methods in Python classes
A method composed of multiple methods that implement the same operation for different types.
Now there is a requirement that requires you to create a custom date class (CustomDate
) in the following ways:
Time stamp
Year, month, day (a tuple containing three integers)
Characters in ISO format String
Datetime
Class
from datetime import date, datetime class CustomDate: def __init__(self, arg): if isinstance(arg, (int, float)): self.__date = date.fromtimestamp(arg) elif isinstance(arg, tuple) and len(arg) == 3 and all(map(lambda x: isinstance(x, int), arg): self.__date = date(*arg) elif isinstance(arg, str): self.__date = date.fromisoformat(arg) elif isinstance(arg, datetime): self.__date = datetime.date() else: raise TypeError("could not create instance from " + type(arg).__name__) @property def date(): return self.__date
Note: Incoming will not be discussed here. Whether the date/time stamp is legal or not, we only make a rough judgment on the type.
We can split different building methods into multiple methods and use the singledispatchmethod
decorator in functools
to decide which one to call based on the type of parameters passed in method.
from datetime import date, datetime from functools import singledispatchmethod class CustomDate: @singledispatchmethod def __init__(self, arg): raise TypeError("could not create instance from " + type(arg).__name__) @__init__.register(int) @__init__.register(float) def __from_timestamp(self, arg): self.__date = date.fromtimestamp(arg) @__init__.register(tuple) def __from_tuple(self, arg): if len(arg) == 3 and all(map(lambda x: isinstance(x, int), arg)): self.__date = date(*arg) else: raise ValueError("could not create instance from a malformed tuple") @__init__.register(str) def __from_isoformat(self, arg): self.__date = date.fromisoformat(arg) @__init__.register(datetime) def __from_datetime(self, arg): self.__date = arg.date() @property def date(self): return self.__date
In this way, we can separate the initialization of each parameter type into separate methods.
Which method implementation should be used during the call is determined by the dispatch algorithm. If the algorithm decides which method implementation to use based only on the type of a single parameter, it is called single dispatch.
singledispatchmethod
It is single dispatch. That is, only the first parameter will be considered. This is far from enough in actual business.
However, as above, we still need to use if
/else
to determine the type of elements in the tuple. That is, we cannot use typing.Tuple[int, int, int]
.
As a compromise, perhaps we can define a ThreeIntTuple
class to limit it and isolate these judgments from the CustomDate
class.
I only provide an idea here for your reference, I will not implement it (because we have a better way xD).
This library is not one of the standard libraries and needs to be installed through pip:
pip install multimethod
multimethod
It uses a multi-dispatch algorithm, which can better meet more complex scenarios. In addition, the library also has good support for types in typing
.
Back to the above question, we can improve it like this:
Use multimethod
method To replace singledispatchmethod
;
Use Tuple[int, int, int]
to replace tuple
, no longer needed Manually verify the length and element type of the tuple;
from datetime import date, datetime from typing import Tuple, Union from multimethod import multimethod class CustomDate: @multimethod def __init__(self, arg): raise TypeError("could not create instance from " + type(arg).__name__) @__init__.register def __from_timestamp(self, arg: Union[int, float]): self.__date = date.fromtimestamp(arg) @__init__.register def __from_tuple(self, arg: Tuple[int, int, int]): self.__date = date(*arg) @__init__.register def __from_isoformat(self, arg: str): self.__date = date.fromisoformat(arg) @__init__.register def __from_datetime(self, arg: datetime): self.__date = arg.date() @property def date(self): return self.__date
Before doing this, ask first A simple question for everyone (this is closely related to our next content):
class A: def a(self): print(1) def a(self): print(2) A().a()
What will the above code output? Or will it throw an error?
Output 2
.
In Python, if methods with duplicate names are defined, the last method will overwrite the previous method.
But you may not know that we can change this behavior through metaclass:
class MetaA(type): class __prepare__(dict): def __init__(*args): pass def __setitem__(self, key, value): if self.get('a'): # Line 7 super().__setitem__('b', value) # Line 8 else: super().__setitem__(key, value) class A(metaclass=MetaA): def a(self): print(1) def a(self): print(2) A().a() # => 1 A().b() # => 2 # Line 22
In lines 7 and 8, we will a## with the same name # The method is renamed
b and is successfully called on line 22. The maintainers of
multimethod have made good use of this and processed methods with duplicate names to achieve a "special effect".
multimethod.multidata to the
CustomDate class Metaclass;
__init__.
from datetime import date, datetime from typing import Tuple, Union from multimethod import multimeta class CustomDate(metaclass=multimeta): def __init__(self, arg: Union[int, float]): self.__date = date.fromtimestamp(arg) def __init__(self, arg: Tuple[int, int, int]): self.__date = date(*arg) def __init__(self, arg: str): self.__date = date.fromisoformat(arg) def __init__(self, arg: datetime): self.__date = arg.date() def __init__(self, arg): raise TypeError("could not create instance from " + type(arg).__name__) @property def date(self): return self.__dateIn terms of effect, this is exactly the same as method overloading in static languages!
The above is the detailed content of How to define multiple constructor method overloading and generic methods in Python classes. For more information, please follow other related articles on the PHP Chinese website!