[issue29113] modulefinder no longer finds all required modules for Python itself, due to use of __import__ in sysconfig

Matthias Klose added the comment: the idea is that we load a different _sysconfigdata module when we are cross building packages. So we don't know the name in advance. An ugly alternative would be a big if statement with conditional imports for all known cross build targets. Not sure if

[issue29113] modulefinder no longer finds all required modules for Python itself, due to use of __import__ in sysconfig

Brett Cannon added the comment: The limitation is unavoidable as modulefinder inspects bytecode for its inferencing, so any code that calls __import__() or importlib.import_module() will simply not work. So unless sysconfig can be updated reasonably back to a statically defined import this is

[issue29113] modulefinder no longer finds all required modules for Python itself, due to use of __import__ in sysconfig

Changes by Ned Deily : -- nosy: +doko versions: +Python 3.7 ___ Python tracker ___ ___

[issue29113] modulefinder no longer finds all required modules for Python itself, due to use of __import__ in sysconfig

New submission from Adam Williamson: I'm not sure if this is really considered a bug or just an unavoidable limitation, but as it involves part of the stdlib operating on Python itself, I figured it was at least worth reporting. In Fedora we have a fairly simple little script called