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 terry.reedy
Recipients ammar2, docs@python, kim.oldfield, terry.reedy
Date 2019-08-22.05:28:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566451716.12.0.139098438709.issue37862@roundup.psfhosted.org>
In-reply-to
Content
Even if click 'Library Reference', click '2. Built-in...', click name in the index at the top of the page to go to the entry I know I want to read is sometimes slower that 'click search box', enter word, hit Return, wait for results, scan results to find that entry, I prefer a consistent and dependable result.

That said, perhaps the search algorithm should start with looking words up in the builtins list, the module index, the glossary, and the index, and display those first  Index pages with definitions should get heavy weight too.  But is seems from your example that the obvious places might be downweighted instead.

As for my answer, I believe that the search once used Google, which was and still is terrible at returning results from the current doc.  For instance, just now, the 2nd return for 'Python zip' is the zip entry in chapter 2 ... for 3.3.7!  'Python zip 3.7' does return
https://docs.python.org/3/library/functions.html
as first entry. I would rather click click to get to the same place.

If Julien and Ammar can improve Search [      ] to beat that, and be consistently useful to beginners, more power to them.
History
Date User Action Args
2019-08-22 05:28:36terry.reedysetrecipients: + terry.reedy, docs@python, ammar2, kim.oldfield
2019-08-22 05:28:36terry.reedysetmessageid: <1566451716.12.0.139098438709.issue37862@roundup.psfhosted.org>
2019-08-22 05:28:36terry.reedylinkissue37862 messages
2019-08-22 05:28:35terry.reedycreate