[issue45396] Custom frozen modules get ignored.

Change by Eric Snow : -- resolution: fixed -> stage: resolved -> patch review status: closed -> open ___ Python tracker ___ ___ Pyt

[issue45396] Custom frozen modules get ignored.

Eric Snow added the comment: The behavior has been addressed in the fix for bpo-45395. However, I'd like to change the name of the -X option from "frozen_modules" to "frozen_stdlib", to avoid any confusion in the future. After that this issue is done. -- resolution: -> fixed stage

[issue45396] Custom frozen modules get ignored.

Change by Eric Snow : -- pull_requests: +27565 pull_request: https://github.com/python/cpython/pull/29301 ___ Python tracker ___ ___

[issue45396] Custom frozen modules get ignored.

Change by Eric Snow : -- pull_requests: +27560 pull_request: https://github.com/python/cpython/pull/28778 ___ Python tracker ___ ___

[issue45396] Custom frozen modules get ignored.

Guido van Rossum added the comment: I'm not convinced by the comment you linked to. It seems Brett is referring to the case where at the C level someone overrides `PyImport_FrozenModules` (a global in frozen.c) -- though it is never explicitly named in the thread. And that variable *is* igno

[issue45396] Custom frozen modules get ignored.

Change by Eric Snow : -- keywords: +patch pull_requests: +27110 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/28776 ___ Python tracker ___

[issue45396] Custom frozen modules get ignored.

Eric Snow added the comment: (This was motivated by https://github.com/python/cpython/pull/28633#discussion_r720506225.) -- ___ Python tracker ___ ___

[issue45396] Custom frozen modules get ignored.

New submission from Eric Snow : Recently we added the "-X frozen_modules" CLI option to control whether or not (non-essential) frozen modules get used. Currently the default is "off", though the plan is to make the default "on". Regardless, this is problematic for executables with custom fr