__init__ file role in Python

Introduction

The __init__.py file tells Python that a folder is a package. It helps organize code into groups.

When you want to group related Python files into one package.

When you want to import code from one folder easily.

When you want to run setup code automatically when a package is imported.

When you want to control what is available when someone imports your package.

Syntax

Python

# __init__.py can be empty or contain code

# Example: initialize a variable
message = 'Hello from package'

# Example: import submodules
from . import module1
from . import module2

The __init__.py file must be inside the folder you want to treat as a package.

It can be empty or have Python code that runs when the package is imported.

Examples

This makes Python treat the folder as a package without extra setup.

Python

# Empty __init__.py file
# Just create an empty file named __init__.py inside the folder

This variable can be accessed when the package is imported.

Python

# __init__.py with a variable
message = 'Welcome to my package!'

This lets you import submodules directly from the package.

Python

# __init__.py importing submodules
from . import tools
from . import helpers

Sample Program

This example shows how __init__.py imports a function from a submodule so you can call it directly from the package.

Python

# Folder structure:
# mypackage/
#   __init__.py
#   greet.py

# Content of greet.py:
# def say_hello():
#     print('Hello from greet module!')

# Content of __init__.py:
from .greet import say_hello

# main.py (outside mypackage folder):
import mypackage

mypackage.say_hello()

Important Notes

Without __init__.py, Python 3.3+ treats folders as implicit namespaces, but explicit __init__.py is still recommended for clarity.

You can put setup code in __init__.py that runs when the package is imported.

Summary

__init__.py marks a folder as a Python package.

It can be empty or contain code to run on import.

It helps organize and control package imports.

Practice

1. What is the main role of a __init__.py file in a Python folder?

easy

A. To mark the folder as a Python package

B. To store global variables for the project

C. To execute the main program code

D. To compile Python files into bytecode

Solution

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

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

2. Step 2: Differentiate from other file roles

   It does not store global variables, run main code, or compile files; its role is to mark the folder as a package.

3. Final Answer:

   To mark the folder as a Python package -> Option A

4. Quick Check:

   __init__.py marks package = C [OK]

Hint: Remember: __init__.py means 'this is a package' [OK]

Common Mistakes:

• Thinking it runs main program code
• Confusing it with a config file
• Assuming it compiles Python files

2. Which of the following is a correct way to create an empty __init__.py file in a package folder?

easy

A. Create a file named __init__.py with no content

B. Create a file named init.py with no content

C. Create a file named __init__.py with a main() function

D. Create a file named __init__.txt with no content

Solution

1. Step 1: Identify the exact filename required

   The file must be named exactly __init__.py to mark the folder as a package.

2. Step 2: Confirm that it can be empty

   The file can be empty; no code is required inside for it to work.

3. Final Answer:

   Create a file named __init__.py with no content -> Option A

4. Quick Check:

   Empty __init__.py file = B [OK]

Hint: Filename must be exactly __init__.py [OK]

Common Mistakes:

• Using wrong filename like init.py or __init__.txt
• Adding unnecessary code inside when empty is fine
• Confusing with main.py or other files

3. Given this folder structure and files:

mypackage/
  __init__.py
  module.py

# __init__.py content:
print('Package imported')

# module.py content:
def greet():
    return 'Hello!'

# main.py content:
import mypackage
from mypackage import module
print(module.greet())

What will be the output when running main.py?

medium

A. Hello!\nPackage imported

B. Package imported\nHello!

C. Hello!

D. ImportError

Solution

1. Step 1: Understand import behavior

   When import mypackage runs, the code inside __init__.py executes, printing 'Package imported'.

2. Step 2: Check subsequent import and function call

   Then from mypackage import module imports the module, and print(module.greet()) prints 'Hello!'.

3. Final Answer:

   Package imported Hello! -> Option B

4. Quick Check:

   Init runs first, then greet() output = A [OK]

Hint: Code in __init__.py runs on package import [OK]

Common Mistakes:

• Assuming __init__.py code does not run
• Mixing order of printed lines
• Expecting ImportError without reason

4. You have a folder named utils with a file helper.py inside. You try to import helper using import utils.helper but get ModuleNotFoundError. What is the most likely cause?

medium

A. The helper.py file has syntax errors

B. The helper.py file is empty

C. You need to run Python with administrator rights

D. The utils folder is missing __init__.py

Solution

1. Step 1: Understand package import requirements

   Python requires an __init__.py file in a folder to treat it as a package for imports like utils.helper.

2. Step 2: Identify cause of ModuleNotFoundError

   If __init__.py is missing, Python does not recognize utils as a package, causing the error.

3. Final Answer:

   The utils folder is missing __init__.py -> Option D

4. Quick Check:

   Missing __init__.py causes import error = D [OK]

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

Common Mistakes:

• Blaming syntax errors without checking
• Thinking admin rights affect imports
• Assuming empty files cause import failure

5. You want to create a package shapes with subpackage polygons. You want importing shapes to automatically import polygons as well. How should you modify shapes/__init__.py to achieve this?

hard

A. Add import shapes.polygons inside shapes/__init__.py

B. Add import polygons inside shapes/__init__.py

C. Add from . import polygons inside shapes/__init__.py

D. Leave shapes/__init__.py empty; Python imports subpackages automatically

Solution

1. Step 1: Understand relative imports in packages

   To import a subpackage inside a package's __init__.py, use relative import syntax like from . import polygons.

2. Step 2: Avoid absolute import inside the package

   Using import polygons or import shapes.polygons may cause errors or circular imports; relative import is preferred.

3. Step 3: Confirm that empty __init__.py does not import subpackages

   Python does not import subpackages automatically; explicit import is needed.

4. Final Answer:

   Add from . import polygons inside shapes/__init__.py -> Option C

5. Quick Check:

   Use relative import from . import polygons = A [OK]

Hint: Use relative import from . import subpackage in __init__.py [OK]

Common Mistakes:

• Using absolute import inside __init__.py
• Expecting automatic subpackage import
• Forgetting to add __init__.py in subpackage