Title: Inability to specific __qualname__ as a property on a class instance.
Type: enhancement Stage: needs patch
Components: Interpreter Core Versions: Python 3.10
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: LewisGaul, grahamd, pitrou
Priority: normal Keywords:

Created on 2013-09-22 13:37 by grahamd, last changed 2021-02-21 00:04 by LewisGaul.

Messages (3)
msg198275 - (view) Author: Graham Dumpleton (grahamd) Date: 2013-09-22 13:37
Python 3 introduced __qualname__. This attribute exists on class types and also instances of certain class types, such as functions. For example:

def f(): pass


class Class: pass




An instance of a class however does not have __name__ or __qualname__ attributes. With:

c = Class()



Traceback (most recent call last):
  File "", line 13, in <module>
AttributeError: 'Class' object has no attribute '__name__'

Traceback (most recent call last):
  File "", line 14, in <module>
AttributeError: 'Class' object has no attribute '__qualname__'

For a class, it is possible to override the __name__ attribute using a property.

class Class:
    def __name__(self):
        return 'override'

c = Class()


With the result being:


This is useful in writing object proxies or function wrappers for decorators as rather than having to copy the __name__ attribute into the wrapper, the lookup can be deferred until when it is required.

The same though cannot be done for __qualname__. With:

class Class:
    def __qualname__(self):
        return 'override'

yielding an error when the class definition is being processed:

Traceback (most recent call last):
  File "", line 16, in <module>
    class Class:
TypeError: type __qualname__ must be a str, not property

This means the same trick cannot be used in object proxies and function wrappers and instead __qualname__ must be copied and assigned explicitly as a string attribute in the __init__() function of the object proxy or function wrapper.

I can sort of understand a prohibition on __qualname__ being a string attribute in certain cases, especially if overriding it on a type or instance where __qualname__ attribute already exists, but I don't understand why a limitation would be imposed to prevent using a property as a means of generating the value for a class instance which doesn't otherwise have a __qualname__ attribute. There is no similar restriction for __name__.

Unless there is a good specific reason for this behaviour, the ability to override it with a property in cases where the __qualname__ attribute didn't already exist, would be handy for proxies and wrappers.
msg198276 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-09-22 13:39
I guess this would be a harmless improvement in any case.
msg387431 - (view) Author: Lewis Gaul (LewisGaul) * Date: 2021-02-21 00:04
This would also be useful for me - I just hit this same problem. If someone could give some guidance on how to make this change I'd be happy to put up a PR.
Date User Action Args
2021-02-21 00:04:59LewisGaulsetnosy: + LewisGaul
messages: + msg387431
2021-02-15 20:09:43iritkatrielsetversions: + Python 3.10, - Python 3.4
2013-09-22 13:39:20pitrousetversions: + Python 3.4, - Python 3.3
nosy: + pitrou

messages: + msg198276

type: behavior -> enhancement
stage: needs patch
2013-09-22 13:37:01grahamdcreate