Why is python mangling here-CodePudding

Why does this code fail if there is no cls. before __TEXT

__TEXT = "abcde"

print(__TEXT)
class aaa():
    @classmethod
    def bbb(cls):
        print(__TEXT)

aaa.bbb()

The output is:

abcde
Traceback (most recent call last):
  File "<string>", line 9, in <module>
  File "<string>", line 7, in bbb
NameError: name '_aaa__TEXT' is not defined

CodePudding user response：

Not quite sure if that was the error, but you can just make the function require a parameter text, that seems to work just fine. You need to give me more information though so I can try to help.

    __TEXT = "abcde"

    print(__TEXT)
    class aaa():
    @classmethod
    def bbb(self, __TEXT):
       print(__TEXT)

    aaa.bbb(__TEXT)

CodePudding user response：

A double underscore prefix causes the Python interpreter to rewrite the attribute name in order to avoid naming conflicts in subclasses.

This is also called "name mangling." The interpreter changes the name of the variable in a way that makes it harder to create collisions when the class is extended later.

Reference docs: https://docs.python.org/3/tutorial/classes.html#private-variables

CodePudding user response：

The Python Interpreter mangles variable-names with a double-underscore to avoid name clashes with variable-names defined by subclasses.

The goal behind this is almost equivalent to final variables in Java and non virtual in C .

Take for instance:

class Human:
    def __init__(self):
        self.surname = 'Jeffrey'
        self._age = 22
        self.__id = 5

# Let's check the variables associated with this class
x = Human()
print(dir(x)) # gives: ['_Human__id', ..., '_age', 'name']

# Create a subclass 'Cook'

class Cook(Human):
    def __init__(self):
        Human.__init__(self)        
        self.__id = 25

y = Cook()
print(dir(y)) # gives: ['_Human__id', '_Cook__id', ..., '_age', 'name']

CodePudding user response：

In PEP 8, they specifically say:

__double_leading_underscore: when naming a class attribute, invokes name mangling (inside class FooBar, __boo becomes _FooBar__boo ...).

Notice the selection in bold. In the exact same sentence where they draw attention to mangling's use in naming class attributes, they state that the mangling happens to any __boo inside of the class, which perfectly explains what you are observing.