Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented May 22, 2025

The __main__ module imported in the _pyrepl module points to the _pyrepl module itself when the interpreter was launched without -m option and didn't execute a module,
while it's an unexpected behavior that __main__ can be _pyrepl and relative imports such as from . import * works based on the _pyrepl module.
(cherry picked from commit b1b8962)

Co-authored-by: Yuichiro Tachibana (Tsuchiya) [email protected]
Co-authored-by: Łukasz Langa [email protected]

…the correct `__main__` module (pythongh-134275)

The `__main__` module imported in the `_pyrepl` module points to the `_pyrepl` module itself when the interpreter was launched without `-m` option and didn't execute a module,
while it's an unexpected behavior that `__main__` can be `_pyrepl` and relative imports such as `from . import *` works based on the `_pyrepl` module.
(cherry picked from commit b1b8962)

Co-authored-by: Yuichiro Tachibana (Tsuchiya) <[email protected]>
Co-authored-by: Łukasz Langa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants