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

[QEDady]

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-139686: Make reloading a lazy module no-op #139857

[ericvsmith]

Please show some example code. Show how it works, and what you expect the behavior to be.

[QEDady]

There is no way to surface the behaviour with the public API. Nevertheless, the private API for _LazyModule should be compatible with importlib.reload. I sent a fix in this PR