When we decorate function, we use functools.wraps to make decorated function look like original.
Is there any wat to do same, when we want to decorate class?
def some_class_decorator(cls_to_decorate):
class Wrapper(cls_to_decorate):
"""Some Wrapper not important doc."""
pass
return Wrapper
@some_class_decorator
class MainClass:
"""MainClass important doc."""
pass
help(MainClass)
Output:
class Wrapper(MainClass)
| Some Wrapper not important doc.
|
| Method resolution order:
| Wrapper
| MainClass
| builtins.object
|
# ... no MainClass important doc below.
I tried to write wraps equivalent for class decorator based on functools.wraps
source code, but my implementation doesn't work correct:
import functools
def wraps_cls(original_cls):
def wrapper(wrapper_cls):
"""Update wrapper_cls to look like original_cls."""
for attr in functools.WRAPPER_ASSIGNMENTS:
try:
value = getattr(original_cls, attr)
except AttributeError:
pass
else:
setattr(wrapper_cls, attr, value)
return wrapper_cls
return wrapper
def some_class_decorator(cls_to_decorate):
@wraps_cls(cls_to_decorate)
class Wrapper(cls_to_decorate):
"""Some Wrapper not important doc."""
pass
return Wrapper
@some_class_decorator
class MainClass:
"""MainClass important doc."""
pass
help(MainClass)
Output:
class MainClass(MainClass)
| MainClass important doc.
|
| Method resolution order:
| MainClass
| MainClass
| builtins.object
|
# ... MainClass doc is here but "Method resolution order" is broken.
Is there anyway to completely replace decorated MainClass help output with not decorated MainClass help output?
No, there isn't, assuming your decorator really subclasses the wrapped class like
some_class_decorator
does. The output ofhelp
is defined by thepydoc.Helper
class, which for classes ultimately callspydoc.text.docclass
, which contains this code:You can see that it is hard-coded to display the class's real MRO. This is as it should be. The MRO displayed in your last example is not "broken", it is correct. By making your wrapper class inherit from the wrapped class, you added an additional class to the inheritance hierarchy. It would be misleading to show an MRO that left that out, because there really is a class there. In your example, this wrapper class doesn't provide any behavior of its own, but a realistic wrapper class would (or else why would you be doing the wrapping at all?), and you would want to know which behavior came from the wrapper class and which from the wrapped class.
If you wanted, you could make a decorator that dynamically renamed the wrapper class with some name derived from the original, so the MRO would show something like
DecoratorWrapper_of_MainClass
in the appropriate position. Whether this would be more readable than just havingWrapper
there is debatable.Oh, I guess now I understand what are your trying to achieve.
You want to attach new methods from a "wrapper" using a class decorator.
Here is a workng example:
This example creates a new class not modifying the old class.
But I guess you could also just inject the given methods in the old class, modifying it in place.