Configure-based build system doesn't have a documented way to disable modules like setup.py did

Feature or enhancement

To provide the ability to disable modules in the configure-based build system like the now removed setup.py did.

Pitch

Until the removal of setup.py, it was possible to disable modules by editing DISABLED_MODULE_LIST.

https://github.com/python/cpython/blob/dcb342b5f9d931b030ca310bf3e175bbc54df5aa/setup.py#L60-L61

In the past I used this to disable _tkinter.

In the configure based system, this is still possible but relies on internal variable names. I can pass py_cv_module__tkinter=disabled to ./configure. It would be useful to have something that was documented rather than having to rely on internal variables like that.

Previous discussion

Not yet, but can do if desired.

まず、リンクされている setup.py の行と、py_cv_module__tkinter=disabled を指定した、文書化されている ./configure の呼び出し周辺の configure ベースのビルドフローを確認します。モジュールを無効化するためのサポート対象インターフェースをどこに文書化すべきか、またそれがカバーすべき既存の動作を特定します。内部変数名に依存せずにユーザーがモジュールを無効化でき、文書がサポート対象のプロセスを反映していれば完了です。