[issue27304] Create "Source Code" links in module sections, where relevant

Terry J. Reedy added the comment: Three of the links are to one- or two- line modules that import the C implementation. I considered dropping them, but decided that the only way to know that they are not worth looking at is to let someone take a look. A counter argument is that we don't have

[issue27304] Create "Source Code" links in module sections, where relevant

Roundup Robot added the comment: New changeset e3b4033e0ea7 by Terry Jan Reedy in branch '3.5': Issue #27304: Source code links for sub-packages in the same file. https://hg.python.org/cpython/rev/e3b4033e0ea7 -- nosy: +python-dev ___ Python tracker

[issue27304] Create "Source Code" links in module sections, where relevant

Terry J. Reedy added the comment: Looks good at first review on Rietveld. Will test next. -- ___ Python tracker ___ ___ Python-bugs-l

[issue27304] Create "Source Code" links in module sections, where relevant

New submission from Yoni Lavi: This is a follow to #22558. As per Terry's suggestion in #22558, for packages with multiple modules that are all documented on the same page and that currently have a "Source Code" link to an __init__ file (e.g. importlib), we should also add more specific "Sour