inspect.getsource returns irrelevant text when used in repl on a class defined in place

[evle-zzz]

Bug report

Bug description:

Run interactive cpython 3.13 with following input.

>>> import inspect
>>> class B: pass
...
>>> inspect.getsource(B)
"# Important: don't add things to this module, as they will end up in the REPL's\n"

Instead of class code we get a piece of repl internals.

CPython versions tested on:

3.13

Operating systems tested on:

Windows

Linked PRs

• gh-126019 Fix inspect.getsource for classes created in PyREPL #126032

[devdanzin]

Seems related to #122071 and its associated issues, probably due to how linecache works.

[evle-zzz]

Just in case, similar small issue nearby:

>>> import dataclasses
>>> inspect.getsource(type(dataclasses)('test'))
Traceback (most recent call last):
  File "<python-input-72>", line 1, in <module>
    inspect.getsource(type(dataclasses)('test'))
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\evlez\AppData\Local\Programs\Python\Python313\Lib\inspect.py", line 1256, in getsource
    lines, lnum = getsourcelines(object)
                  ~~~~~~~~~~~~~~^^^^^^^^
  File "C:\Users\evlez\AppData\Local\Programs\Python\Python313\Lib\inspect.py", line 1238, in getsourcelines
    lines, lnum = findsource(object)
                  ~~~~~~~~~~^^^^^^^^
  File "C:\Users\evlez\AppData\Local\Programs\Python\Python313\Lib\inspect.py", line 1060, in findsource
    file = getsourcefile(object)
  File "C:\Users\evlez\AppData\Local\Programs\Python\Python313\Lib\inspect.py", line 963, in getsourcefile
    filename = getfile(object)
  File "C:\Users\evlez\AppData\Local\Programs\Python\Python313\Lib\inspect.py", line 924, in getfile
    raise TypeError('{!r} is a built-in module'.format(object))
TypeError: <module 'test'> is a built-in module

"built-in" is misleading here. That's actually a regular module.

[devdanzin]

"built-in" is misleading here. That's actually a regular module.

We could check object.__spec__ (which is None for modules created in the REPL like you did). If there is a __spec__ then object.__spec__.origin can point to a source file, contain the string "(built-in)" or the string "(frozen)". That would allow for a better description of the module type in the error message.

Should we open a new issue for this?