Understanding the Differences Between import and from ... import in Python

Learn about the differences between importing modules in Python and how to effectively manage your imports to avoid NameErrors.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Form A import B and import A causes troubles

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving the Import Confusion in Python

Python is a powerful programming language, but sometimes it can trip developers up, especially when it comes to importing modules. A common problem you might encounter is the confusion arising from the different ways to import modules and functions. In this guide, we will explore the case where using import can lead to a NameError, while from ... import works perfectly fine. We'll clarify the issues and guide you through how to fix it.

The Problem

Let's consider a situation where we have a folder structure like the following:

[[See Video to Reveal this Text or Code Snippet]]

[[See Video to Reveal this Text or Code Snippet]]

This works seamlessly! However, the moment you switch to:

[[See Video to Reveal this Text or Code Snippet]]

You receive the error:

[[See Video to Reveal this Text or Code Snippet]]

What's Going Wrong?

The crux of the problem lies in how Python handles different import statements. Let's break down this behavior.

Understanding Import Statements

1. The import module Statement

When you use import utils, you are importing the entire module named utils. However, this method has two notable characteristics:

Clarity: This method keeps things clear about where functions originate, making it easier to understand the source of each function when reading the code.

Example:

[[See Video to Reveal this Text or Code Snippet]]

2. The from module import ... Statement

On the other hand, when you use from utils import function_a, function_b:

Direct Access: You can directly access function_a and function_b without needing to prefix them with the module name.

Less Clarity: The downside is that when someone reads your code, it might not be immediately clear where function_a or function_b was defined, since they do not show the module prefix.

Example:

[[See Video to Reveal this Text or Code Snippet]]

How to Fix the NameError

Option 1: Use the import Statement

If you prefer to import the entire module, then make sure to use the qualified name:

[[See Video to Reveal this Text or Code Snippet]]

Option 2: Use the from ... import Statement

If you want to keep your code concise and avoid typing the module name repeatedly, you can stick to:

[[See Video to Reveal this Text or Code Snippet]]

This method is convenient for smaller scripts where clarity of function origin is less of a concern.

Conclusion

Understanding the differences between import and from ... import is crucial for effective Python programming. By recognizing how each method affects your code structure and function access, you can avoid pitfalls like the NameError encountered in your script. Choose the importing technique that best suits your needs, and you'll streamline your coding process while maintaining clarity. Happy coding!