Package structure and usage in Python - Time & Space Complexity

Time Complexity: Package structure and usage

O(n)

Understanding Time Complexity

When working with packages in Python, it's important to know how the structure affects the time it takes to import and use code.

We want to understand how the time to load and access parts of a package changes as the package grows.

Scenario Under Consideration

Analyze the time complexity of importing modules from a package with multiple submodules.

# package/__init__.py
from .module1 import func1
from .module2 import func2

# module1.py
def func1():
    return "Hello from module1"

# module2.py
def func2():
    return "Hello from module2"

# main.py
from package import func1, func2
print(func1())
print(func2())
    

This code shows importing functions from different modules inside a package and using them.

Identify Repeating Operations

Look at what happens when importing the package:

• Primary operation: Importing each module listed in the package's __init__.py
• How many times: Once per module during the import process

How Execution Grows With Input

As the number of modules in the package increases, the import time grows roughly in proportion.

Number of Modules (n)	Approx. Import Operations
10	10 module imports
100	100 module imports
1000	1000 module imports

Pattern observation: Import time grows linearly as more modules are imported.

Final Time Complexity

Time Complexity: O(n)

This means the time to import grows directly with the number of modules you import from the package.

Common Mistake

[X] Wrong: "Importing a package always takes the same time, no matter how many modules it has."

[OK] Correct: Each module imported runs its code once, so more modules mean more work and longer import time.

Interview Connect

Understanding how package structure affects import time helps you write cleaner, faster-loading code and shows you think about efficiency in real projects.

Self-Check

"What if the package uses lazy imports inside functions instead of importing all modules at once? How would the time complexity change?"

Practice

1. What is the main purpose of the __init__.py file in a Python package?

easy

A. To mark a directory as a Python package

B. To execute the main program

C. To store global variables

D. To compile Python files

Solution

1. Step 1: Understand the role of __init__.py

   The __init__.py file tells Python that the directory should be treated as a package.

2. Step 2: Differentiate from other options

   It does not execute the main program, store global variables, or compile files; its main role is package identification.

3. Final Answer:

   To mark a directory as a Python package -> Option A

4. Quick Check:

   __init__.py marks packages [OK]

Hint: Remember: __init__.py makes folder a package [OK]

Common Mistakes:

• Thinking __init__.py runs main code automatically
• Confusing it with a script file
• Assuming it compiles Python files

2. Which of the following is the correct way to import the module utils from a package named mypackage?

easy

A. import mypackage.utils

B. from utils import mypackage

C. import utils.mypackage

D. from mypackage import utils

Solution

1. Step 1: Recall Python import syntax for packages

   To import a module from a package, use from package_name import module.

2. Step 2: Match syntax to options

   from mypackage import utils matches this syntax: from mypackage import utils.

3. Final Answer:

   from mypackage import utils -> Option D

4. Quick Check:

   Import module with 'from package import module' [OK]

Hint: Use 'from package import module' to import modules [OK]

Common Mistakes:

• Reversing package and module names
• Using incorrect import order
• Trying to import module as package

3. Given this package structure:

mypackage/
  __init__.py
  math_ops.py
  string_ops.py

And this code:

from mypackage import math_ops
print(math_ops.add(2, 3))

If math_ops.py contains a function def add(a, b): return a + b, what is the output?

medium

A. None

B. TypeError

C. 5

D. NameError

Solution

1. Step 1: Understand the import and function call

   The code imports math_ops from mypackage and calls math_ops.add(2, 3).

2. Step 2: Evaluate the function output

   The function add returns the sum of 2 and 3, which is 5.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   2 + 3 = 5 [OK]

Hint: Trace function call and return value carefully [OK]

Common Mistakes:

• Forgetting to call the function with parentheses
• Confusing module and function names
• Assuming import fails without __init__.py content

4. You have a package folder named tools with modules calc.py and format.py. You try to run:

from tools import calc
print(calc.multiply(4, 5))

But get ModuleNotFoundError. What is the most likely cause?

medium

A. Function multiply does not exist in calc.py

B. Missing __init__.py file in the tools folder

C. Syntax error in import statement

D. Python version is too old

Solution

1. Step 1: Understand ModuleNotFoundError cause

   This error often means Python does not recognize the folder as a package.

2. Step 2: Check package structure requirements

   Without __init__.py, Python won't treat 'tools' as a package, causing import failure.

3. Final Answer:

   Missing __init__.py file in the tools folder -> Option B

4. Quick Check:

   __init__.py missing causes ModuleNotFoundError [OK]

Hint: Always add __init__.py to package folders [OK]

Common Mistakes:

• Assuming function absence causes ModuleNotFoundError
• Ignoring package folder structure
• Blaming Python version without checking files

5. You want to create a package datautils with submodules clean.py and transform.py. You want users to import clean_data function directly from datautils like this:

from datautils import clean_data

Which code should you add to datautils/__init__.py to enable this?

hard

A. from .clean import clean_data

B. import clean_data from clean

C. from clean import clean_data

D. import clean.clean_data

Solution

1. Step 1: Understand relative imports in packages

   Inside __init__.py, use relative import with dot: from .clean import clean_data.

2. Step 2: Confirm correct syntax for exposing functions

   This syntax makes clean_data available directly from datautils.

3. Final Answer:

   from .clean import clean_data -> Option A

4. Quick Check:

   Use 'from .module import func' in __init__.py [OK]

Hint: Use relative import with dot in __init__.py [OK]

Common Mistakes:

• Using absolute import without dot inside __init__.py
• Wrong import syntax like 'import clean_data from clean'
• Trying to import without __init__.py setup