PCAP Modules and Packages Practice Test 5 — 15 Questions

Question 1

Consider the following directory structure:
project/
  main.py
  pkg/
    __init__.py
    mod1.py
    subpkg/
      __init__.py
      mod2.py
From main.py, you write: from pkg.subpkg import mod2
Which THREE of the following are true regarding relative imports?

Accepted Answer

Relative imports only work when the importing module is part of a package.. Relative imports (using dot notation like `..` or `.`) are only valid when the importing module is itself part of a package. This is because relative imports rely on the `__package__` attribute to resolve the import path; if the module is not inside a package (e.g., a top-level script), `__package__` is `None` or empty, and relative imports will raise an `ImportError`.

Answer

In main.py, you can use `from . import pkg` to import pkg.

Answer

A directory must contain an __init__.py file to be a package for relative imports to function.

Question 2

You are working on a Python project that uses multiple third-party packages. One of your scripts imports 'requests' and 'numpy'. You notice that when you run your script, it uses the system-wide installed versions, but you want to use versions installed in a virtual environment. You have already activated the virtual environment using `source venv/bin/activate`, and `which python` points to the virtual environment's Python. However, when you import 'requests', it still uses the global version. What is the most likely reason?

Accepted Answer

The PYTHONPATH environment variable is set to the global site-packages.. When PYTHONPATH includes the global site-packages directory, those paths are inserted at the beginning of sys.path, ahead of the virtual environment's site-packages. Therefore, even with the virtual environment activated and the correct Python interpreter, the import system finds the global package first and loads it instead of the venv version. The --system-site-packages flag alone does not place global packages before venv packages; it appends them after.

Answer

The virtual environment's site-packages directory is not first in sys.path because the system site-packages are still included due to the --system-site-packages option or a misconfiguration.

Answer

The packages are not installed in the virtual environment; they are only listed in pip list erroneously.

Answer

The script is being run with the system Python instead of the virtual environment's Python.

Question 3

Your team is developing a large application with many packages. To avoid name conflicts, you decide to use namespace packages. You have two directories: /team/common/ and /team/analytics/. Both contain an __init__.py file. You want to create a namespace package 'team' that combines these two directories. You create a directory /team/ with no __init__.py. You then set PYTHONPATH to /team/common/ and /team/analytics/ (actually, you set it to the parent directories). But when you try to `from team.common import something`, you get ModuleNotFoundError. What is the most likely reason?

Accepted Answer

The PYTHONPATH should point to the parent directory of 'team', not to the subdirectories directly.. For namespace packages to work, PYTHONPATH must point to the parent directory of the 'team' namespace package, not to the subdirectories 'common' and 'analytics' directly, and not to the 'team' directory itself. When PYTHONPATH includes '/team/common/' and '/team/analytics/', Python treats each as a separate top-level package, so 'from team.common import something' fails because 'team' is not found as a package. The correct setup is to set PYTHONPATH to the directory that contains the 'team' directory (e.g., the parent of /team), allowing Python to discover 'team' as a namespace package and then locate 'common' and 'analytics' as sub-packages.

Answer

The presence of __init__.py in 'common' and 'analytics' prevents them from being part of a namespace package.

Answer

The namespace package requires an __init__.py in the parent directory as well.

Answer

The sys.path must also include the 'team' directory itself.

Question 4

What is the most likely cause of this error?

Accepted Answer

Circular import between __init__.py and submodule.py.. A circular import occurs when `__init__.py` and `submodule.py` attempt to import each other (directly or indirectly) before either module is fully initialized. In Python, when a module is being imported, it is added to `sys.modules` as a partially initialized module; if another module tries to import it during that time, it may receive an incomplete or empty module object, leading to an `ImportError` or `AttributeError`. This is a common cause of import failures in packages where initialization logic in `__init__.py` depends on submodules that themselves import from the package root.

Answer

The package's __init__.py is missing a __all__ definition.

Answer

The main.py is executed from a directory outside the package.

Answer

The submodule.py attempts to import a module named '__init__' which is reserved.

Answer

The submodule.py uses an invalid relative import syntax.

Question 5

A team is developing a large application that consists of multiple components, each housed in separate directories. They want to organize these components under a common namespace package called 'app'. The directory structure is as follows:

/opt/project/
├── components/
│   ├── auth/         (contains __init__.py and modules)
│   └── billing/      (contains __init__.py and modules)
├── main.py
└── another_location/
    └── reports/      (contains __init__.py and modules)

The team wants to allow all these components to be imported as subpackages of 'app', e.g., 'import app.auth', 'import app.billing', 'import app.reports'. They have ensured that none of the directories named 'app' exist; instead, they plan to use namespace packages. They create a directory '/opt/project/app/' with an __init__.py file, and move the auth and billing directories under it. However, the reports directory must remain at '/opt/project/another_location/reports/', but they want it to be accessible as 'app.reports'. They attempt to achieve this by adding '/opt/project/another_location/' to the sys.path. When they run main.py, they get an ImportError: No module named 'app.reports'. The auth and billing modules work fine. What is the most likely issue and the correct fix?

Accepted Answer

The reports package needs to be moved under the app directory physically.. For 'app.reports' to be importable, the reports directory must reside inside an 'app' directory on one of the sys.path entries. Adding '/opt/project/another_location/' to sys.path makes a top-level 'reports' package importable, not 'app.reports'. The presence of __init__.py in the app directory is irrelevant here; even if removed, Python cannot find reports as a subpackage because there is no 'app' directory in another_location. The necessary fix is to physically move the reports package under the app directory (or create an app directory in another_location and place reports inside it, then remove __init__.py for namespace merging).

Answer

The sys.path modification is not persistent; they need to set the PYTHONPATH environment variable.

Answer

The reports directory has an __init__.py file, which conflicts with the namespace package.

Answer

The app directory has an __init__.py file, which prevents it from being a namespace package. Remove the __init__.py from the app directory.

Question 6

A Python script imports the module 'my_module'. The developer wants to ensure that when the script is run directly, it executes a specific function, but when imported as a module, that function is not executed. Which code snippet achieves this?

Accepted Answer

if __name__ == '__main__': run(). Both options A and B are correct because they are identical and represent the standard Python idiom `if __name__ == '__main__': run()`. When the script is run directly, Python sets `__name__` to `'__main__'`, triggering the function. When imported, `__name__` is the module name, so the function is not executed. Options C and D are incorrect: C relies on an environment variable that is not standard, and D checks `sys.argv[0]` which is the script path, not the module name.

Answer

if os.environ.get('RUN_MAIN'): run()

Answer

if sys.argv[0] == 'my_module': run()

Question 7

A developer notices that a custom package 'mypackage' is not being found when importing, even though it is installed in the site-packages directory. The developer suspects a conflict with another package of the same name. Which command should the developer run to diagnose the location from which Python is importing the package?

Accepted Answer

print(mypackage.__file__). `mypackage.__file__` returns the filesystem path from which the module was loaded, allowing the developer to see exactly which `mypackage` Python is using. This directly reveals if the wrong package (e.g., from a different location or a conflicting installation) is being imported instead of the intended one.

Answer

print(mypackage)

Answer

print(__file__)

Answer

import os; print(os.getcwd())

Question 8

Which TWO of the following are valid ways to import a module named 'math' and give it an alias 'm'?

Accepted Answer

import math as m. Only B. Option B uses the correct syntax `import math as m` to import the entire math module with alias m. Option A is invalid because the asterisk (*) cannot be combined with an alias in a `from ... import` statement. Option C is missing the `as` keyword. Option D uses `alias` which is not a valid keyword; the correct keyword is `as`. Option E imports a specific function (sin) from math, not the module itself; therefore it does not satisfy the requirement to import the module and give it an alias.

Answer

from math import * as m

Answer

import math m

Answer

import math alias m

Answer

from math import sin as m

Question 9

Which THREE of the following statements about Python packages and modules are true?

Accepted Answer

A module is a single .py file containing Python definitions and statements.. A module in Python is defined as a single .py file that contains Python definitions, such as functions, classes, and variables, as well executable statements. This is the fundamental unit of code organization in Python, and any .py file can be imported as a module.

Answer

The sys.path list is read-only and cannot be modified at runtime.

Answer

A package must contain an __init__.py file to be importable.

Question 10

You are a developer at a company that builds a data processing pipeline. The pipeline consists of several Python modules organized in a package called 'pipeline'. The package structure is:

pipeline/
    __init__.py
    load.py
    transform.py
    analyze.py

The pipeline is deployed on a server where Python 3.8 is installed. The server also has a globally installed package called 'pipeline' (from a different project) in the site-packages directory. When you run your scripts that import 'pipeline', you get unexpected behavior because Python is importing the wrong package. You need to ensure that your local 'pipeline' package is used instead of the global one. You cannot uninstall the global package because it is used by another application. You have the following options:

A) Modify the PYTHONPATH environment variable to include the directory containing your 'pipeline' package before the site-packages directory.
B) Rename your local 'pipeline' package to something else and update all imports.
C) Use a virtual environment specific to your project and install your package there.
D) Add an __init__.py file with a special import hook to override the global package.

Which course of action is the most appropriate and reliable?

Accepted Answer

Use a virtual environment specific to your project and install your package there.. Using a virtual environment creates an isolated Python environment where you can install your local 'pipeline' package without affecting or being affected by the globally installed package. This is the most reliable approach as it ensures that Python's import system will search the virtual environment's site-packages before the global site-packages, preventing any naming conflicts. Virtual environments are the standard Python best practice for managing project-specific dependencies and avoiding package name collisions.

Answer

Modify the PYTHONPATH environment variable to include the directory containing your 'pipeline' package before the site-packages directory.

Answer

Rename your local 'pipeline' package to something else and update all imports.

Answer

Add an __init__.py file with a special import hook to override the global package.

Question 11

A Python package 'mypackage' contains the following hierarchy:

mypackage/
    __init__.py
    subpackage1/
        __init__.py
        module_a.py
    subpackage2/
        __init__.py
        module_b.py

From a script outside the package, a programmer writes:

import mypackage.subpackage1.module_a

Which statement is true about the import?

Accepted Answer

Both mypackage/__init__.py and mypackage/subpackage1/__init__.py are executed.. When Python encounters an import statement with a dotted path like `import mypackage.subpackage1.module_a`, it executes the `__init__.py` files for each package in the path in order: first `mypackage/__init__.py`, then `mypackage/subpackage1/__init__.py`. This is because Python must initialize each package before it can access its subpackages or modules. Option D correctly states that both `__init__.py` files are executed.

Answer

Only mypackage/__init__.py is executed.

Answer

No __init__.py files are executed because the import uses a dotted path.

Answer

After the import, 'mypackage' is not available as a name in the namespace.

Question 12

A developer has a module 'config.py' with the following content:

# config.py
import os
DATABASE_URL = os.getenv('DATABASE_URL', 'localhost')

Another module 'app.py' imports config and uses DATABASE_URL. During testing, the environment variable is set correctly, but the import still uses the default value 'localhost'. What is the most likely reason?

Accepted Answer

Python caches modules; config.py was imported earlier without the environment variable, and the cached version is reused.. Python caches imported modules in `sys.modules`. If `config.py` was imported earlier in the test session (e.g., during test discovery or another import) before the environment variable `DATABASE_URL` was set, the cached module would retain the default value `'localhost'`. Subsequent imports, even after setting the environment variable, reuse the cached module, so `os.getenv('DATABASE_URL', 'localhost')` is not re-evaluated.

Answer

The import statement in app.py is placed inside a function, so it is not executed.

Answer

The module was imported using 'from config import DATABASE_URL' which creates a separate copy.

Answer

The environment variable is only read when the function is called, not at import time.

Question 13

A developer is writing a package that contains multiple modules. The package should allow users to import it directly and have all commonly used functions available at the package level. For example, after `import mypackage`, the user should be able to call `mypackage.func1()` without needing to import submodules. Which is the best way to achieve this?

Accepted Answer

In `__init__.py`, import the desired functions from the submodules, e.g., `from .submodule import func1`.. `__init__.py` is executed when a package is imported, and importing functions from submodules into `__init__.py` makes them directly accessible as attributes of the package object. This allows `mypackage.func1()` to work without requiring the user to import submodules explicitly, satisfying the requirement of a flat namespace at the package level.

Answer

Create a wrapper function in `__init__.py` that delegates calls to the submodule functions.

Answer

Include `__all__` in each submodule and ensure `__init__.py` is empty.

Answer

Define a list named `__all__` in the package's `__init__.py` that lists the functions.

Question 14

Which TWO of the following statements about Python's `sys.path` are true?

Accepted Answer

Module search stops at the first matching directory in `sys.path`.. Python's import mechanism iterates through `sys.path` in order and stops at the first directory containing the requested module. Option E is correct: the directory containing the script (or the current directory when running interactively) is inserted at the beginning of `sys.path` at startup. Options A, C, and D are false: the current working directory is not always first (the script's directory takes precedence), `sys.path` is initialized from the `PYTHONPATH` environment variable *in addition to* default paths, and `sys.path` is a list, not a tuple. Therefore, only two statements are true.

Answer

The current working directory is always the first element in `sys.path`.

Answer

`sys.path` is initialized from the PYTHONPATH environment variable.

Answer

`sys.path` is a tuple of strings.

Question 15

You are developing a Python application that processes financial transactions. The application is structured as a package named `finance`. Inside `finance`, there are subpackages: `models`, `services`, and `utils`. The `services` subpackage contains a module `validator.py` that defines a function `validate_transaction()`. This function uses a helper function `check_amount()` defined in `utils.helpers`. The package is used by multiple other projects, and you want to ensure that importing `finance` does not accidentally expose internal helper functions. You also want to allow users to easily import the main validation function via `from finance import validate_transaction`. Which of the following approaches best achieves these goals?

Accepted Answer

In `finance/__init__.py`, write `from .services.validator import validate_transaction`. Then users can call `finance.validate_transaction()`.. It imports the `validate_transaction` function directly into the `finance` package namespace via `from .services.validator import validate_transaction` in `finance/__init__.py`. This allows users to use `from finance import validate_transaction` as desired, while keeping internal helper functions like `check_amount` in `utils.helpers` unexposed, since they are not imported into the package's top-level namespace. This approach follows the principle of explicit imports and encapsulation.

Answer

In `finance/__init__.py`, write `from . import services` and `from .services import validator`. Then users can call `finance.services.validator.validate_transaction()`.

Answer

In `finance/__init__.py`, write `from .services import validator`. Then users can call `finance.validator.validate_transaction()`.

Answer

In `finance/__init__.py`, write `from .utils.helpers import *` and `from .services.validator import validate_transaction`.