Reloading a lazy module that has not yet been materailized should be no-op

Bug report

Bug description:

Reloading a not-yet materialized lazy module is not supported well. It makes sense for the reloading in this case to be no-op since when the actual loading happens e.g. by accessing an attribute, the new code will be loaded anyway. Currently, the reload tries to reload the module while its loaded is lazy in the first place.

CPython versions tested on:

3.13, 3.12, 3.14, CPython main branch

Operating systems tested on:

Linux

Linked PRs

• gh-139857
• gh-142649
• gh-143584

首先查看链接的 PR gh-139857、gh-142649 和 gh-143584，因为它们展示了针对这一行为已经提出的工作。跟踪 lazy module 的 reload 路径，并验证在 materialization 之前 reload 是 no-op，而之后的属性访问仍会加载更新后的代码；完成时应包括回归覆盖。