Bug report

Bug description:

importosprint("FILE",os.__file__,os.__spec__)deflocalImportFailure():try:fromosimportlistdir,listdir2,pathexceptExceptionase:print("gives",type(e),repr(e))print("From import that fails in the middle",end=" ")localImportFailure()

This code outputs with 3.13.1 the following:

FILE C:\Python313_64\Lib\os.py ModuleSpec(name='os', loader=<class '_frozen_importlib.FrozenImporter'>, origin='frozen')From import that fails in the middle gives <class 'ImportError'> ImportError("cannot import name 'listdir2' from 'os' (unknown location)")

As you can see, the__file__ and__spec__ values are fine. I found this in a regression test of Nuitka which worked with 3.13.1 and all Python versions before, giving the proper path from Python (which I use as a test oracle to know what the behavior to compare against is).

From my look at the code, this "unknown location" is coming from a code path, that tries to recognize shadowed stdlib modules, a new feature added in 3.13.1, can you please consider repairing it for 3.13.2, as I think file paths are very important part of exceptions for developers.

The issue is not OS specific. It only occurs with 3.13.1, not with 3.13.0.

CPython versions tested on:

3.13

Operating systems tested on:

Windows

Linked PRs

• gh-127651: Use __file__ in diagnostics if origin is missing #127660
• [3.13] gh-127651: Use __file__ in diagnostics if origin is missing (#127660) #127775