Compiling a package which PYTHON_SINGLE_TARGET differs from that of gobject-introspection results in: File "/usr/bin/g-ir-scanner", line 99, in <module> from giscanner.scannermain import scanner_main File "/usr/lib64/gobject-introspection/giscanner/scannermain.py", line 35, in <module> from giscanner.ast import Include, Namespace File "/usr/lib64/gobject-introspection/giscanner/ast.py", line 29, in <module> from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib64/gobject-introspection/giscanner/sourcescanner.py", line 33, in <module> from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' Reproducible: Always
(In reply to Eugene Shalygin from comment #0) > Compiling a package which PYTHON_SINGLE_TARGET differs from that of [...] What packages are those?
Could be any of 209 packages in the main tree...
(In reply to Jeroen Roovers from comment #2) > Could be any of 209 packages in the main tree... If you mean there are 209 packages that depend on dev-libs/gobject-introspection, then probably all of them. While upgrating to python 3.8 I encountered the error with dev-libs/libpeas and media-gfx/gimp before I understood where is the problem and reverted glib-based apps to python 3.7.
The original bug report has nothing to do with python3.8 support, but PYTHON_SINGLE_TARGET not being fully honored or something. I have never seen this problem from main tree for many years, but often see it from gobject-introspection coming from some unofficial overlay, due to not properly handling g-ir-scanner shebang with python-single-r1. Given that, lack of emerge --info to confirm, and that python3.8 support is already there since almost a month, closing this bug.
