QUERY · ISSUE

BUG: sys.modules['sys'] not pointing import('sys')

openby pmp-popened 2019-07-16updated 2019-07-16

Probably the same reason as :
https://github.com/micropython/micropython/issues/4427

CANDIDATE · ISSUE

BUG: sys.modules['main'] not pointing import('main')

openby pmp-popened 2019-01-25updated 2025-03-03

proposed-closeneeds-info

cpython automatically gives access to sys.modules[__name__] from module '__main__' and returns value of __import__('__main__').

micropython does not and forces to use__import__(__name__) which is not a good way to get a module by fully qualified name ( eg when getting a dot package name you only get toplevel ).

Assessment

S Sonnet · high

Issue #4923 (sys.modules['sys'] vs import('sys')) and #4427 (sys.modules['main'] vs import('main')) share the same root cause — MicroPython's module system does not consistently register built-in modules in sys.modules under the same object returned by import. The query author explicitly acknowledges this ("Probably the same reason as #4427"). However, they are distinct manifestations affecting different modules (sys vs main), so a fix for one does not necessarily resolve the other. They are RELATED rather than DUPLICATE.

Suggested action

Link the two issues as related in both. If a fix is implemented that resolves the general module registration inconsistency (covering all built-in modules), both can be closed together. Otherwise, track separately per affected module.

BUG: sys.modules['sys'] not pointing __import__('sys')

BUG: sys.modules['__main__'] not pointing __import__('__main__')

Keyboard

BUG: sys.modules['sys'] not pointing import('sys')

BUG: sys.modules['main'] not pointing import('main')