Non-package module loaded from ModInfo object retains __path__ from previously loaded package.

Bug report

Assume you have two separate modules with the same name. One is a package, one is not.

Use pkgutil.itermodules to get a ModuleInfo object for the package, then load the it using find_module and load_module. This object has a __path__ object with the location of package, as expected.

Next, do the same for the non-package module. The resulting module object should have no __path__ attribute, but instead it has one with the location of the package opened previously.

This can be replicated with a structure such as \module\submodule\submodule.py, using \module and \module\submodule as the arguments for the two calls to pkgutil.itermodules.

Your environment

• CPython versions tested on: 3.10.7, 3.11.0rc2
• Operating system and architecture: Windows 10

使用 issue 中描述的两种模块布局，通过先调用 pkgutil.itermodules，再调用 find_module 和 load_module，重现该行为。比较 package 和 non-package 模块对象；完成的标准是 non-package 模块不再保留之前加载的 package 的 path。