gh-101100: Fix load_module ref
#114982
gh-101100: Fix load_module ref
#114982
Conversation
Text describes a user-provided method, perhaps only described in detail in `PEP 302`.
|
As I stated in #114729 (comment), this method is described in detail at https://docs.python.org/3/library/importlib.html#importlib.abc.Loader.load_module. But I don't think either suppressing this link or linking to https://docs.python.org/3/library/importlib.html#importlib.abc.Loader.load_module would be the correct way to resolve this reference warning. This glossary entry appears pretty out of date to me; |
|
The discussion around |
Yes, we already had this conversation in #114729 (comment). And I still think the best way to correct this reference warning is to update the glossary entry so that it no longer refers to a deprecated method at all. If that requires an importlib expert, then we should wait for an importlib expert to take a look. |
|
I will let @AlexWaygood and @serhiy-storchaka sort this out. Let me know your collective decision and I'll change the ref to suit so we can close out this PR. |
|
I agree that it is better to not refer to the deprecated method. But this requires the larger change that simply adding the exclamation mark. So this Sphinx warnings serves as a reminder to rewrite the docs. |
Exactly. I would prefer that we leave this Sphinx warning unfixed for now, until we are able to fix it properly, by updating the entry so that it no longer refers to a deprecated method. I said this in #114729 (comment) and #114982 (comment) |
|
Closing. Will let others decide how best to correct this. |
Text describes a user-provided method, perhaps only described in detail in
PEP 302.📚 Documentation preview 📚: https://cpython-previews--114982.org.readthedocs.build/