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 kim.oldfield
Recipients docs@python, kim.oldfield, terry.reedy
Date 2019-08-22.02:41:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566441685.51.0.757510493583.issue37862@roundup.psfhosted.org>
In-reply-to
Content
Usually the search page is the quickest way to find documentation about a module or function - quicker than navigating through a couple of levels of pages (documentation home, index, index by letter, scroll or search in page to find desired name, click on name).

Searching for builtin functions is inconsistent. Some functions (eg getattr) are found as expected in a search, while other functions (eg zip and many others) aren't found in the search results. This could easily lead someone to incorrectly concluding that the function they are search for doesn't exist in python.

I find the response of "The search page is the last thing one should use" strange. Surely as the option to search is there, and it mostly works, we should be making incremental improvements as necessary to make it better so that everyone can easily find the right parts of the python documentation.
History
Date User Action Args
2019-08-22 02:41:25kim.oldfieldsetrecipients: + kim.oldfield, terry.reedy, docs@python
2019-08-22 02:41:25kim.oldfieldsetmessageid: <1566441685.51.0.757510493583.issue37862@roundup.psfhosted.org>
2019-08-22 02:41:25kim.oldfieldlinkissue37862 messages
2019-08-22 02:41:25kim.oldfieldcreate