Skip to content

pip search <pkg> follows PyPI relevance ordering #7260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zachvalenta opened this issue Oct 25, 2019 · 1 comment
Closed

pip search <pkg> follows PyPI relevance ordering #7260

zachvalenta opened this issue Oct 25, 2019 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@zachvalenta
Copy link

zachvalenta commented Oct 25, 2019

What's the problem this feature will solve?

  • more relevant search results
  • current search doesn't return main package from query or few results from PyPI search

Describe the solution you'd like

current

$ pip3 search ansible  
ansible-toolkit (1.3.2)            - The missing Ansible tools
ansible-alicloud (1.11.0)          - Ansible provider for Alicloud.
ansible-toolset (0.7.0)            - Useful Ansible toolset

results ordered following PyPI relevance ranking https://pypi.org/search/?q=ansible

$ pip3 search ansible
ansible (2.8.6)                    - Radically simple IT automation system
ansible-bundle (0.7.0)             - Manage ansible role and modules versioned dependencies.
ansible-docgenerator (0.1.0)       - Simple tool for generating ansible role documentation
@ghost ghost added the S: needs triage Issues/PRs that need to be triaged label Oct 25, 2019
@chrahunt
Copy link
Member

chrahunt commented Dec 8, 2019

Hi @zachvalenta. There are some links over in #6842 (comment) that give context - different implementations are used between the PyPI website search and the search API used by pip. I would file an issue over on pypa/warehouse (the project behind PyPI) suggesting that the XMLRPC search API return the same results as the website. That sounds reasonable to me, but there's probably some things I'm not considering (like any personalization, for example).

I hope that helps! Since it doesn't look like there's anything we can do in pip here I will close this, but please drop a link to any related issues or discussions.

@chrahunt chrahunt closed this as completed Dec 8, 2019
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jan 7, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jan 7, 2020
@ghost ghost removed the S: needs triage Issues/PRs that need to be triaged label Jan 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

2 participants