Name mangling in Python - Time & Space Complexity

Time Complexity: Name mangling

O(1)

Understanding Time Complexity

Let's explore how the time it takes to run code changes when using name mangling in Python.

We want to see how the program's steps grow as the input or usage grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class MyClass:
    def __init__(self, value):
        self.__hidden = value

    def get_hidden(self):
        return self.__hidden

obj = MyClass(10)
print(obj.get_hidden())

This code uses name mangling to hide a variable inside a class and then accesses it through a method.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing the mangled variable inside the method.
• How many times: Once per method call; no loops or recursion here.

How Execution Grows With Input

Since there are no loops or repeated steps, the time to access the mangled name stays about the same no matter what.

Input Size (n)	Approx. Operations
10	About 1 access
100	About 1 access
1000	About 1 access

Pattern observation: The time does not grow with input size; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means the time to access a mangled name is constant and does not depend on input size.

Common Mistake

[X] Wrong: "Name mangling makes accessing variables slower because of extra steps."

[OK] Correct: Name mangling just changes the variable name internally; accessing it is still a simple, direct operation.

Interview Connect

Understanding how name mangling works and its performance helps you explain how Python handles private variables clearly and confidently.

Self-Check

"What if the method accessed the mangled variable inside a loop running n times? How would the time complexity change?"

Practice

1. What does name mangling do to an attribute starting with double underscores in a Python class?

easy

A. It adds the class name before the attribute name to avoid conflicts.

B. It makes the attribute public and accessible everywhere.

C. It deletes the attribute from the class.

D. It converts the attribute name to uppercase.

Solution

1. Step 1: Understand double underscore prefix

   Attributes starting with double underscores trigger name mangling in Python classes.

2. Step 2: Effect of name mangling

   Python adds the class name before the attribute name to avoid accidental access or conflicts.

3. Final Answer:

   It adds the class name before the attribute name to avoid conflicts. -> Option A

4. Quick Check:

   Name mangling = adds class name prefix [OK]

Hint: Double underscores add class name prefix to attribute [OK]

Common Mistakes:

• Thinking double underscores make attribute public
• Confusing name mangling with deleting attributes
• Assuming attribute name changes to uppercase

2. Which of the following is the correct way to define a private attribute using name mangling in a Python class?

easy

A. self.__my_attr = 5

B. def __my_attr(self): pass

C. self._my_attr = 5

D. self.my_attr__ = 5

Solution

1. Step 1: Identify private attribute syntax

   Private attributes use double underscores at the start of the name, like __my_attr.

2. Step 2: Check correct assignment

   Assigning with self.__my_attr = 5 correctly defines a private attribute with name mangling.

3. Final Answer:

   self.__my_attr = 5 -> Option A

4. Quick Check:

   Double underscore prefix = private attribute [OK]

Hint: Use double underscores before attribute name for private [OK]

Common Mistakes:

• Using single underscore instead of double
• Placing underscores after attribute name
• Defining private attribute as a method incorrectly

3. What will be the output of this code?

class A:
    def __init__(self):
        self.__x = 10

a = A()
print(hasattr(a, '__x'))
print(hasattr(a, '_A__x'))

medium

A. True\nTrue

B. False\nTrue

C. True\nFalse

D. False\nFalse

Solution

1. Step 1: Check attribute __x existence

   Due to name mangling, __x is stored as _A__x internally, so hasattr(a, '__x') returns False.

2. Step 2: Check mangled attribute _A__x existence

   hasattr(a, '_A__x') returns True because this is the mangled name storing the value.

3. Final Answer:

   False True -> Option B

4. Quick Check:

   __x hidden as _A__x = False, True [OK]

Hint: Check mangled name with _ClassName__attr [OK]

Common Mistakes:

• Assuming __x is directly accessible
• Confusing mangled name with original
• Expecting both hasattr calls to be True

4. What is the error in this code snippet?

class B:
    def __init__(self):
        self.__val = 5

b = B()
print(b.__val)

medium

A. SyntaxError due to double underscores

B. No error, prints 5

C. TypeError because __val is private

D. AttributeError because __val is name mangled

Solution

1. Step 1: Understand name mangling effect

   __val is mangled to _B__val internally, so b.__val does not exist.

2. Step 2: Accessing __val causes AttributeError

   Trying to print b.__val raises AttributeError because the attribute is hidden by name mangling.

3. Final Answer:

   AttributeError because __val is name mangled -> Option D

4. Quick Check:

   Accessing __val directly = AttributeError [OK]

Hint: Access mangled attribute with _ClassName__attr [OK]

Common Mistakes:

• Expecting no error when accessing __val
• Thinking double underscores cause syntax error
• Confusing AttributeError with TypeError

5. Given this class:

class C:
    def __init__(self):
        self.__data = 42
    def get_data(self):
        return self.__data

c = C()

How can you access the private attribute __data from outside the class without using the get_data method?

hard

A. c.__data

B. c._data

C. c._C__data

D. c.get_data()

Solution

1. Step 1: Understand name mangling for __data

   The attribute __data is stored internally as _C__data due to name mangling.

2. Step 2: Access mangled attribute directly

   You can access it from outside the class using c._C__data.

3. Final Answer:

   c._C__data -> Option C

4. Quick Check:

   Access private with _ClassName__attr [OK]

Hint: Use _ClassName__attr to access private attribute [OK]

Common Mistakes:

• Trying to access c.__data directly
• Using single underscore _data instead
• Confusing method call with attribute access