PCAP Modules and Packages Practice Test 1 — 15 Questions

Question 1

A developer is working on a project that requires the use of a third-party package hosted on a private repository. The developer wants to ensure that the package can be imported without specifying the full repository URL each time. Which approach should be taken?

Accepted Answer

Configure the repository URL in pip's configuration file or in requirements.txt.. Option C is correct because configuring the repository URL in pip's configuration file (e.g., `pip.conf`, `pip.ini`, or `~/.config/pip/pip.conf`) or in `requirements.txt` using the `--index-url` or `--extra-index-url` option allows pip to resolve the package from the private repository automatically. This approach ensures that the package can be installed and imported without manually specifying the full URL each time, as pip will use the configured index to locate and download the package.

Answer

Append the repository path to sys.path in the script.

Answer

Place the package files in the site-packages directory manually.

Answer

Use os.system to run a pip install command from within the script.

Question 2

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(). Option B is correct because the `if __name__ == '__main__':` guard is the standard Python idiom to check whether a script is being run directly (as the main program) or being imported as a module. When the script is executed directly, Python sets the special variable `__name__` to the string `'__main__'`, so the function `run()` is called. When the script is imported, `__name__` is set to the module's name (e.g., `'my_module'`), so the condition fails and `run()` is not executed.

Answer

if __name__ == '__main__': run()

Answer

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

Answer

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

Question 3

A developer creates a package named 'analytics' with the following structure:

analytics/
    __init__.py
    stats.py
    models/
        __init__.py
        regression.py

The developer wants the statement 'from analytics import *' to import only the functions 'mean' and 'std' from stats.py. What should be added to analytics/__init__.py?

Accepted Answer

__all__ = ['mean', 'std']. Option D is correct because in Python, the `__all__` variable in a package's `__init__.py` explicitly controls which names are exported when `from package import *` is used. By setting `__all__ = ['mean', 'std']`, the developer ensures that only the functions `mean` and `std` from `stats.py` are imported into the namespace, as Python will look up these names in the package's scope after executing the `__init__.py` file. This overrides the default behavior where all public names (those not starting with an underscore) would be exported.

Answer

Nothing; by default, all names are exported.

Answer

from analytics.stats import *

Answer

__all__ = ['stats.mean', 'stats.std']

Question 4

A developer is troubleshooting an ImportError: 'No module named 'config''. The config module is located in a subdirectory 'utils' relative to the script. The script's current working directory is the parent of 'utils'. Which of the following lines, added to the script, will resolve the issue?

Accepted Answer

sys.path.append('utils'). The ImportError occurs because Python's module search path (sys.path) does not include the 'utils' subdirectory. Adding 'utils' to sys.path via sys.path.append('utils') tells Python to look inside that directory for modules, resolving the import. Option B is correct because it extends the search path to include the directory containing the config module, without altering the script's working directory or incorrectly appending a file path.

Answer

sys.path.append('utils/config.py')

Answer

sys.path = os.path.join(sys.path, 'utils')

Answer

os.chdir('utils')

Question 5

A developer wants to import a specific function 'calculate' from a module named 'formulas' without importing the entire module. Which import statement should be used?

Accepted Answer

from formulas import calculate. Option C is correct because the `from module import name` syntax in Python allows you to import a specific function (or other attribute) from a module directly into the current namespace, without importing the entire module. This avoids unnecessary memory usage and keeps the namespace clean by only bringing in the needed `calculate` function.

Answer

import formulas

Answer

import calculate from formulas

Answer

import formulas as f

Question 6

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__). Option C is correct because `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 7

A developer is creating a package that contains a subpackage. The subpackage has an __init__.py file that imports a module named 'helper' from the parent package. Which import statement in the subpackage's __init__.py will correctly import 'helper'?

Accepted Answer

from mypackage import helper. Option A is correct because the subpackage's __init__.py needs to import the 'helper' module from the parent package using an absolute import. The statement 'from mypackage import helper' explicitly references the parent package by its name, which is the standard way to import from a parent package when the package structure is known and avoids ambiguity with relative imports.

Answer

from . import helper

Answer

from ... import helper

Answer

from .. import helper

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. Option B is correct because the `import ... as` syntax is the standard Python way to import a module and assign it an alias. This allows you to refer to the module's contents using the shorter alias `m` instead of the full module name `math`.

Answer

from math import * as m

Answer

import math m

Answer

import math alias 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.. Option C is correct because 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.. Option A is correct because 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

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

Answer

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

Answer

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

Question 11

A developer is troubleshooting a Python application that fails to import a custom module named 'utils'. The file 'utils.py' exists in the same directory as the main script. Which of the following is the most likely cause of the import failure?

Accepted Answer

The directory containing utils.py is not in sys.path.. When Python imports a module, it searches for it in the directories listed in sys.path. Even if 'utils.py' is in the same directory as the main script, that directory may not be automatically included in sys.path if the script is not run as a module (e.g., using python main.py from a different working directory). The most common cause of such a failure is that the script's directory is missing from sys.path, which prevents Python from locating the file.

Answer

There is a circular import between utils.py and the main script.

Answer

The directory lacks an __init__.py file.

Answer

The utils.py file contains a syntax error.

Question 12

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 13

A programmer wants to create a package named 'analytics' with subpackages 'statistics' and 'ml'. Which directory structure correctly defines these packages?

Accepted Answer

analytics/ (__init__.py), analytics/statistics/ (__init__.py), analytics/ml/ (__init__.py). In Python, a directory is recognized as a package only if it contains an `__init__.py` file (even if empty). To create the 'analytics' package with 'statistics' and 'ml' subpackages, each directory must have its own `__init__.py`. Option D correctly places `__init__.py` in all three directories: `analytics/`, `analytics/statistics/`, and `analytics/ml/`.

Answer

analytics/, analytics/statistics/ (__init__.py), analytics/ml/ (__init__.py)

Answer

analytics/ (__init__.py), analytics/statistics/ (__init__.py), analytics/ml/ (__init__.py), analytics/__init__.py (file)

Answer

analytics/ (__init__.py), analytics/statistics/, analytics/ml/

Question 14

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.. Option D is correct because 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 15

A Python package 'shapes' has the following __init__.py:

# shapes/__init__.py
from .circle import Circle
from .square import Square

A user writes:

import shapes
c = shapes.Circle(5)

This works correctly. However, when the user writes:

import shapes.circle
c = shapes.circle.Circle(5)

It fails with AttributeError: module 'shapes' has no attribute 'circle'. What is the most likely reason?

Accepted Answer

The submodule 'circle' is not added to the package's namespace because the __init__.py does not import it as a submodule.. Option A is correct because when a package's __init__.py imports specific names (like Circle) from submodules, it does not automatically make the submodule itself accessible as an attribute of the package. The submodule 'circle' is not added to the package's namespace unless explicitly imported as a submodule (e.g., using 'import shapes.circle' in __init__.py). Thus, 'import shapes.circle' fails because Python cannot find 'circle' in the package's namespace.

Answer

The __init__.py file must include 'import shapes.circle' to make the submodule accessible.

Answer

The submodule name 'circle' conflicts with the class name 'Circle' due to case sensitivity.

Answer

The import statement 'import shapes.circle' is invalid because submodules must be imported using 'from' syntax.