New REPL sets global `__package__` to `'_pyrepl'`

[sobolevn]

Python 3.14.0a0 (heads/main-dirty:a2d0818c85c, Sep 10 2024, 22:19:41) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> __package__
'_pyrepl'

Python 3.11.9 (main, Jun 29 2024, 11:57:49) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> __package__ is None
True

I am not sure that this is a bug. But it might be.
Please, feel free to close if this is expected.

[sobolevn]

This also happens:

>>> import inspect
>>> def func():
...     frame = inspect.currentframe()
...     print(frame.f_globals)
...     
>>> func()
{'__package__': '_pyrepl', ...}

[sobolevn]

cc @ambv and @pablogsal

[pablogsal]

I'm not fully sure this qualifies as a bug. Unsetting this can be quite painful because it can mess up with using PyREPL as a module which we use quite often to check for coverage or profile.

@ambv what do you think?

[ambv]

I don't think we can reasonably do anything here. It's a change in behavior, sure, but it stems directly from how Python works. In your example, Nikita, __file__ points at _pyrepl/__main__.py, which is indeed what we are running as the REPL globals() now.