[SOLVED] What places other than sys.path python looks for when importing a package

What places other than sys.path python looks for when importing a package

Scenario

From a package let's say beta:
After modifying the sys.path, importing a package alpha then reverting the sys.path. I try to import a module data_provider that exists in both alpha and beta

The issue is: the data_provider in alpha gets picked over beta even though sys.path now has no traces of alpha's directories

Question: Is that a bug, or there's some other places than sys.path (may be caches) that python looks at when trying to import a module

Code

import os, sys

sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)),"src"))

sys.path.insert(0, '../alpha')
import alpha
sys.path.remove('../alpha')

import data_provider as dp

print(sys.path)
print(dp.__file__)

The full codebase could be found here

Solution

The first place checked during import search is sys.modules. This mapping serves as a cache of all modules that have been previously imported, including the intermediate paths. So if foo.bar.baz was previously imported, sys.modules will contain entries for foo, foo.bar, and foo.bar.baz. Each key will have as its value the corresponding module object.

During import, the module name is looked up in sys.modules and if present, the associated value is the module satisfying the import, and the process completes. However, if the value is None, then a ModuleNotFoundError is raised. If the module name is missing, Python will continue searching for the module.