Python Module Stream Default Change in AlmaLinux 9.4 and Its Effect on Kickstart Provisioning

Goal: achieve a repeatable development environment where the system Python interpreter version is predictable across fresh installations and automated image builds.

Constraint: AlmaLinux 9.4 changed the default dnf module stream for the python package from 3.9 to 3.11, a change documented in the 9.4 release notes under Application Streams. However, it remains unclear whether the python:3.11 stream is automatically enabled during a Kickstart‑based installation when no module stream is explicitly specified, leading to potential divergence between generic minimal installs and Kickstart files that omit the stream.

Uncertainty: without explicit stream handling, provisioning tools may install different Python versions depending on the media or automation used, compromising reproducibility.

Does the AlmaLinux 9.4 installer enable the python:3.11 stream by default in a Kickstart installation when no stream is declared? If not, what determines the selected stream in that scenario? How can administrators lock the stream to guarantee identical Python versions across both generic and Kickstart provisioning methods?