Python3自定义包导入问题：动态转项目为包并全局调用

It’s frustrating when you’ve added your project root to sys.path but still can’t import your modules—let’s walk through the most common fixes for this problem.

1. Add __init__.py Files to Define Proper Packages #

Even though Python 3.3+ supports implicit namespace packages, adding empty __init__.py files to your project folders ensures they’re recognized as regular packages, which avoids many import quirks. Your updated structure should look like this:

/home/pavarine/Projects/brp/
├── __init__.py  # Add this empty file
├── config.py
├── main.py
└── lib/
    ├── __init__.py  # Add this empty file too
    └── Class1.py

These files don’t need any code—they just signal to Python that these directories are part of your custom package.

2. Use Correct Absolute Import Statements #

Once your project root is in sys.path, you need to reference modules by their full path relative to the root. For example:

• To import Class1 from the lib folder in main.py:

  from lib.Class1 import Class1
  

• To import variables/functions from config.py:

  import config
  # Or target specific items:
  from config import database_url, load_settings
  

Don’t try to import Class1 directly without the lib. prefix—Python won’t know where to find it unless it’s in the same directory as your running script.

3. Avoid Relative Imports When Running as a Script #

If you’re using relative imports like from .lib.Class1 import Class1 in main.py, this will fail when you run main.py as a standalone script (since scripts are treated as top-level modules). Stick to absolute imports when working with scripts that need to be executed from arbitrary locations.

4. Check for Naming Conflicts #

Make sure there’s no other module or package named lib or Class1 in your existing sys.path. Python prioritizes modules found earlier in the path, so a conflicting name elsewhere will override your custom module. Verify where Python is pulling the module from with this code:

import lib
print(lib.__file__)

If this output doesn’t point to /home/pavarine/Projects/brp/lib, you’ve got a naming conflict to resolve.

5. Better Long-Term Solution: Install in Editable Mode #

Instead of manually manipulating sys.path every time, install your package in editable mode using pip. This adds it to your Python’s site-packages directory, so you can import it from anywhere without path hacks. Run this command in your terminal:

pip install -e /home/pavarine/Projects/brp

Now you can import your modules from any script like this:

from brp.lib.Class1 import Class1
from brp import config

This is the cleanest way to work with custom packages you’re actively developing.

内容的提问来源于stack exchange，提问作者Pavarine