__init__ file role in Python - Cheat Sheet & Quick Revision

Recall & Review

beginner

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

The __init__.py file tells Python that the directory should be treated as a package. It can also initialize package-level variables or import submodules.

beginner

True or False: Without an __init__.py file, Python cannot recognize a folder as a package.

False. Since Python 3.3+, folders without __init__.py can be treated as namespace packages.

intermediate

Can __init__.py contain executable code? What is a common use for this?

Yes, __init__.py can contain executable code. A common use is to initialize package variables or import specific classes/functions to simplify access.

beginner

What happens if __init__.py is empty?

If __init__.py is empty, the folder is still recognized as a package, but no initialization code runs.

intermediate

How does __init__.py help with importing submodules in a package?

By importing submodules inside __init__.py, you can make them available directly when importing the package, making code cleaner and easier to use.

What does the __init__.py file do in a Python folder?

A Compiles Python code

B Runs the main program

C Deletes the folder contents

D Marks the folder as a Python package

The __init__.py file marks the folder as a package so Python can import from it.

Can __init__.py contain code that runs when the package is imported?

A No, it must be empty

B Yes, it can contain initialization code

C Only comments are allowed

D It only contains variable declarations

Yes, __init__.py can contain code that runs when the package is imported.

If __init__.py is missing, what happens when you try to import the folder as a package?

A Python ignores the folder

B Python raises an ImportError

C Python treats it as a package anyway

D Python converts it to a module

Since Python 3.3, without __init__.py, Python treats the folder as a namespace package.

How can __init__.py simplify importing submodules?

A By importing submodules inside __init__.py

B By compiling submodules

C By renaming submodules

D By deleting submodules automatically

Importing submodules inside __init__.py allows users to access them directly from the package.

Is it mandatory to have __init__.py in Python 3.12+ packages?

A No, but recommended for explicit packages

B No, it is deprecated

C Yes, always mandatory

D Only for Python 2

In modern Python, __init__.py is not strictly mandatory but recommended to explicitly mark packages.

Explain the role of the __init__.py file in a Python package.

Think about how Python knows a folder is a package.

Describe how __init__.py can be used to simplify imports in a package.

Consider how you want to access parts of a package easily.

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