Import statement behavior in Python - Time & Space Complexity

Time Complexity: Import statement behavior

O(n)

Understanding Time Complexity

When we use import statements in Python, it's important to understand how the time to load modules grows as the number of imports increases.

We want to know how the program's start-up time changes when importing many modules.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import module1
import module2
import module3

# Imagine many more imports here

print("Modules imported")

This code imports several modules before running the main program.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loading and initializing each imported module.
• How many times: Once for each import statement executed.

How Execution Grows With Input

Each import adds a fixed amount of work to load that module.

Input Size (n)	Approx. Operations
10	About 10 module loads
100	About 100 module loads
1000	About 1000 module loads

Pattern observation: The total work grows directly with the number of imports.

Final Time Complexity

Time Complexity: O(n)

This means the time to import modules grows in a straight line as you add more imports.

Common Mistake

[X] Wrong: "Importing many modules happens instantly and does not affect program speed."

[OK] Correct: Each import requires loading and running code once, so more imports mean more work and longer start-up time.

Interview Connect

Understanding how imports affect program start-up helps you write efficient code and manage dependencies well.

Self-Check

What if we used import inside a function instead of at the top? How would the time complexity change when calling that function multiple times?

Practice

1. What happens when you use import module_name in Python?

easy

A. The module is copied into your current file.

B. Only the functions you call from the module are loaded.

C. The module code runs every time you call a function from it.

D. The entire module is loaded and its code runs once.

Solution

1. Step 1: Understand import behavior

   When you import a module, Python loads the whole module and runs its code once.

2. Step 2: Recognize module reuse

   After the first import, Python reuses the loaded module without running its code again.

3. Final Answer:

   The entire module is loaded and its code runs once. -> Option D

4. Quick Check:

   Import runs module once = A [OK]

Hint: Import runs module code once, then reuses it [OK]

Common Mistakes:

• Thinking module code runs every time a function is called
• Believing only used functions are loaded
• Assuming module code is copied into current file

2. Which of the following is the correct syntax to import only the sqrt function from the math module?

easy

A. from math import sqrt

B. import math.sqrt

C. import sqrt from math

D. from sqrt import math

Solution

1. Step 1: Recall import syntax for specific functions

   To import a specific function, use from module import function.

2. Step 2: Match syntax to options

   from math import sqrt matches this syntax: from math import sqrt.

3. Final Answer:

   from math import sqrt -> Option A

4. Quick Check:

   Specific import uses 'from module import item' = A [OK]

Hint: Use 'from module import name' to import parts [OK]

Common Mistakes:

• Using dot notation in import statement incorrectly
• Swapping module and function names
• Using 'import' with 'from' in wrong order

3. Consider two files:

# file1.py print('Loading file1') value = 10
# file2.py import file1 import file1 print(file1.value)

What is the output when running file2.py?

medium

A. Loading file1
Loading file1
10

B. Loading file1
10

C. 10
10

D. Error: module imported twice

Solution

1. Step 1: Understand module import behavior

   Python runs the module code only once, even if imported multiple times.

2. Step 2: Trace the output

   On first import, 'Loading file1' prints. Second import does nothing. Then prints value 10.

3. Final Answer:

   Loading file1 10 -> Option B

4. Quick Check:

   Module code runs once, reused later = B [OK]

Hint: Module code runs once, even if imported multiple times [OK]

Common Mistakes:

• Expecting module code to run twice
• Thinking repeated imports cause errors
• Confusing print output order

4. What is wrong with this code?

import math from math import sqrt print(math.sqrt(16))

medium

A. You cannot import the same module twice.

B. The code will cause a NameError.

C. There is no error; the code runs and prints 4.0.

D. You must use only one import style per module.

Solution

1. Step 1: Check import statements

   Importing the same module twice with different styles is allowed and does not cause error.

2. Step 2: Verify function call

   Calling math.sqrt(16) works and returns 4.0.

3. Final Answer:

   There is no error; the code runs and prints 4.0. -> Option C

4. Quick Check:

   Multiple imports allowed; function call works = D [OK]

Hint: Multiple imports of same module are allowed [OK]

Common Mistakes:

• Thinking multiple imports cause errors
• Confusing import styles must be exclusive
• Expecting NameError from this code

5. You have a module config.py with a variable setting = 5. In your main program, you do:

import config config.setting = 10 import config print(config.setting)

What will be printed and why?

hard

A. 10, because the module is loaded once and changes persist.

B. Error, because you cannot assign to module variables.

C. 5, because the second import reloads the module resetting variables.

D. None, because the variable is not accessible after import.

Solution

1. Step 1: Understand module import caching

   Python loads a module once and caches it; subsequent imports reuse the same module object.

2. Step 2: Analyze variable assignment and import

   Changing config.setting to 10 modifies the cached module. The second import does not reload, so the change remains.

3. Final Answer:

   10, because the module is loaded once and changes persist. -> Option A

4. Quick Check:

   Module cached; changes persist = C [OK]

Hint: Module imports cache; variable changes stay across imports [OK]

Common Mistakes:

• Assuming second import reloads module
• Thinking module variables are immutable
• Believing variable becomes inaccessible