This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.snow
Recipients brett.cannon, eric.snow, lemburg
Date 2021-10-06.20:21:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1633551663.5.0.531821025802.issue45395@roundup.psfhosted.org>
In-reply-to
Content
The mechanism to add custom frozen modules to the Python runtime is to set PyImport_FrozenModules (see Python/frozen.c) to some new array.  This means that the default frozen modules (from _PyImport_FrozenModules) are no longer used unless explicitly added to the custom array.  This is unlikely to be what the user wants.  It's especially problematic since it's easy to not realize this (or forget) and forgetting essential modules (like _frozen_importlib) will cause crashes.

It would probably make more sense to have PyImport_FrozenModules be an array of *additional* frozen modules, defaulting to an empty array.  Before going down that route we need to be sure that isn't going to break folks that are accommodating the existing behavior.
History
Date User Action Args
2021-10-06 20:21:03eric.snowsetrecipients: + eric.snow, lemburg, brett.cannon
2021-10-06 20:21:03eric.snowsetmessageid: <1633551663.5.0.531821025802.issue45395@roundup.psfhosted.org>
2021-10-06 20:21:03eric.snowlinkissue45395 messages
2021-10-06 20:21:03eric.snowcreate