This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author boris
Recipients boris, docs@python
Date 2021-02-12.23:09:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1613171393.51.0.627157963271.issue43212@roundup.psfhosted.org>
In-reply-to
Content
We can use shpinx.ext.linkcode to link classes and functions/methods to their source code on GitHub from the documentation. See linked PR for screen shots. This is far from linking all the symbols in the docs, but it's gets quite a few. It would be hard to get to 100% because of C modules that get re-exported in Python files.

It slighty increase the time it takes to generate the documentation with `make html`. I get 1m33s with these changes vs 1m28s without them.

One thing is that when you merge a PR on GitHub, any files it touches will have the wrong line numbers while the documentation is being re-built and deployed. That's mostly neglible since most files haven't been edited in the last couple of minutes, but if it's an issue it may be possible to set up the CI to build the documentation then deploy the docs and merge the PR at the same time.
History
Date User Action Args
2021-02-12 23:09:53borissetrecipients: + boris, docs@python
2021-02-12 23:09:53borissetmessageid: <1613171393.51.0.627157963271.issue43212@roundup.psfhosted.org>
2021-02-12 23:09:53borislinkissue43212 messages
2021-02-12 23:09:53boriscreate