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 JelleZijlstra
Recipients AlexWaygood, Dutcho, JelleZijlstra, docs@python, eric.araujo, ethan.furman, meersuri, python-dev
Date 2022-02-10.15:17:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644506232.62.0.0333774034554.issue46586@roundup.psfhosted.org>
In-reply-to
Content
> How do I find other instances of this problem? Is there a systematic way to look for such references?

You could write a script that goes something like this, iterating over all the docs RST files:

- Find all definitions in the file (e.g. `.. decorator:: property`)
- Filter to those that have names that also appear in builtins
- Find any links using those names within the same file

That would catch the enum.property case, but not the float_info one Éric noticed, because sys.rst doesn't define `max` at all. To catch that one, you could look at the link role: sys.rst links to it with :const:`max`, but functions.rst defines it as `.. function:: max`. Mismatches like that could be another clue that something is wrong (but there are some legitimate reasons why the roles won't match perfectly, like "decorator" in the definition vs. "func" in the link).
History
Date User Action Args
2022-02-10 15:17:12JelleZijlstrasetrecipients: + JelleZijlstra, eric.araujo, docs@python, ethan.furman, python-dev, Dutcho, AlexWaygood, meersuri
2022-02-10 15:17:12JelleZijlstrasetmessageid: <1644506232.62.0.0333774034554.issue46586@roundup.psfhosted.org>
2022-02-10 15:17:12JelleZijlstralinkissue46586 messages
2022-02-10 15:17:12JelleZijlstracreate