PCAP Modules and Packages Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  from app.operations.math_ops import calculate

  Why this is correct

  The from-import statement directly fetches the 'calculate' attribute from the 'app.operations.math_ops' module and binds it in the current namespace. This is the most common and concise way to bring a function into scope, and it bypasses the need to reference the module path each time. The import system locates the module using the dotted path, then performs attribute lookup for the function.

• ✓

  import importlib; module = importlib.import_module('app.operations.math_ops'); module.calculate()

  Why this is correct

  The importlib.import_module call enables dynamic import using a string, returning the module object rather than binding it under a fixed name. After calling it, 'module' refers to the same module object that a static import would produce, and you must use attribute access to call 'calculate' because import_module does not unpack the module's contents. This approach is useful for plugins or configurable imports where the module path is not known until runtime.

• ✗

  import app.operations.math_ops.calculate

  Why it's wrong here

  The statement 'import app.operations.math_ops.calculate' is invalid because Python's import statement treats each dotted segment as a module or package name. Functions are attributes of modules, not sub-modules, so this syntax tries to find a module named 'calculate' inside 'math_ops' and raises a ModuleNotFoundError. To import a function, you must use the from-import form or manually reference the attribute after importing the module.

• ✗

  from app.import operations.math_ops import calculate

  Why it's wrong here

  This line is a syntax error because the word 'import' appears after 'from' and again before the function name; the grammar is 'from <module> import <object>', and it allows only one 'import'. Additionally, the dotted path 'app.import operations.math_ops' contains a space and an invalid component 'import', which Python's parser rejects immediately. Even without the space, you cannot place 'import' inside the module path.

• ✓

  import app.operations.math_ops; app.operations.math_ops.calculate()

  Why this is correct

  This two-statement approach imports the top-level module chain and then uses the full dotted path to access the function. Python's import machinery executes the import of 'app.operations.math_ops' and binds the name 'app' in the local (or global) namespace, making subsequent attribute access possible. While slightly verbose, it is a perfectly valid alternative that keeps the module in scope for repeated, namespaced calls.

Go deeper

Related to this question