My package doesn't appear in the search results anymore

[ewdurbin]

Originally reported by: Luca Rebuffi (Bitbucket: lucarebuffi, GitHub: lucarebuffi)

---

I am maintaining packages named "Oasys" and "ShadowOui" in the Pypi site since several months. These packages are available by query with the keyword "oasys".

Since a couple of weeks the result of the query with the keyword and eventually with their names directly does not contain the last versions. On the contrary, all the previous versions, also the ones I deleted are shown. Paradoxically, the command "pip install " finds the correct last version.

---

• Bitbucket: https://bitbucket.org/pypa/pypi/issue/397

[ewdurbin]

Original comment by Vaibhav Kohli (Bitbucket: vaibhavkohli91, GitHub: Unknown):

---

I am facing the same issue for my new package Liota, which is getting listed on web search as well as getting installed but not showing up in the pypi search.

[ewdurbin]

Original comment by anatoly techtonik (Bitbucket: techtonik, GitHub: techtonik):

---

Won't see all constraints in the equation and won't solve it.

[ewdurbin]

Original comment by anatoly techtonik (Bitbucket: techtonik, GitHub: techtonik):

---

You are right. The way to fundraise is through Gratipay (US) or Liberapay (EU), but first it should be discussed how to help. Nadia Eghbal (@nayafia) is researching topic, so reaching out to people first - making it the mafia way - become best friends with developers - may help to at least bootstrap the process. )

Note that bus factor is already in effect, so I guess the best chance is to arrange a meeting at PyCon or EuroPython, but, for example, I can not afford going there even though I have a plenty of time to write here - it is "spending your time" dilemma, you see, and money was invented to solve that conflict. Nobody want to support free beer for "consumers" - it was fun in the old days when people were drinking it together in a real world, but now they grab it and consume alone, and you have no fun dealing with those barbarian people of new age. I guess the root of the problem is that people are "forced" to use open source, not to create it.

So fundraising ans support is still a communication/coordination problem, and it requires financial management effort and skills that historically very unusual for open source people, so unless we find the time to invest into communication and sync, we won't see all those additional constraints that are pressing developers these days.

[ewdurbin]

Original comment by Christian Münker (Bitbucket: Chipmuenk, GitHub: Chipmuenk):

---

Underfunding - sometimes I forget that somebody has to pay for the free beer. Sorry for trolling. But PyPI is one of the most important projects for the python community - there has to be some way of fund raising?

Bus factor - that is really bad :-(

[ewdurbin]

Original comment by anatoly techtonik (Bitbucket: techtonik, GitHub: techtonik):

---

1. underfunding
2. bus factor

[ewdurbin]

Original comment by Christian Münker (Bitbucket: Chipmuenk, GitHub: Chipmuenk):

---

PyDigger is an alternative at least for me - pyfda package is found without problem. How can it be that PyPI cannot list its own packages while external software can?! For months and months?!!

[ewdurbin]

Original comment by Christian Münker (Bitbucket: Chipmuenk, GitHub: Chipmuenk):

---

Same problem with pyfda package, does not appear in search results but can be installed and is also found by google.

[ewdurbin]

Original comment by Michael Howitz (Bitbucket: icemac, GitHub: icemac):

---

@unixsurfer: PyDigger is refreshingly fast but has its own problems. I found the following in the first minutes using it:

• It knows only about 12k packages of about 60k packages on PyPI. (It only lists three out of the ten packages I have on PyPI.)
• The "last page" link leads to an HTTP-500.

In future it could be an alternative but not yet.

[ewdurbin]

Original comment by Pavlos Parissis (Bitbucket: unixsurfer, GitHub: unixsurfer):

---

Search works fine on http://pydigger.com/

[ewdurbin]

Original comment by Alexey T (Bitbucket: neverwalkaloner, GitHub: neverwalkaloner):

---

Same problem with virgil_sdk package, it doesn't appear in the search results.

[ewdurbin]

Original comment by Pavlos Parissis (Bitbucket: unixsurfer, GitHub: unixsurfer):

---

I have a similar problem where my packages [1] don't show up when I search them using their names. pip install works fine. A google search with 'python haproxytool' returns 1st result the pypi page.

[1] anycast-healthchecker, haproxyadmin, haproxystats and haproxytool

[ewdurbin]

Original comment by Dreas Nielsen (Bitbucket: rdnielsen, GitHub: rdnielsen):

---

This issue also affects execsql: web search and pip search only show outdated versions of the package that have been removed some time ago.

[ewdurbin]

Original comment by Ренат Ахмеров (Bitbucket: rakhmerov, GitHub: rakhmerov):

---

Same problem with mistral, mistral-extra, mistral-dashboard and python-mistralclient

[ewdurbin]

Original comment by Fred Stluka (Bitbucket: fredstluka, GitHub: fredstluka):

---

Yeah, same problem here. But I get a much more accurate answer from the script I found here:

• http://code.activestate.com/recipes/577708-check-for-package-updates-on-pypi-works-best-in-pi

and from the command:

pip list --outdated

BTW, there are lots of people complaining of the same problem at Issue #326.

--Fred

[ewdurbin]

Original comment by Brian O'Neill (Bitbucket: Twangist, GitHub: Twangist):

---

Same issue with my package. When I search for log_calls, PyPI shows only the previous version, log_calls 0.2.5.post3, supposedly hidden. The latest version is 0.3.0, supposedly the only version visible, uploaded 1 month+ ago. I can go to its page by URL: pypi.python.org/pypi/log_calls goes to the page for 0.3.0. The page for the previous version correctly lists 0.3.0 as the latest version. pip will install the latest version without specifying any version (I haven't tried it today, but I have done it.)

[ewdurbin]

Original comment by Senthil Muniswamy (Bitbucket: smuniswamy, GitHub: smuniswamy):

---

Same issue with ncryptify package. Current latest version 0.0.8 is not listed upon search. Only lists the earlier versions that are supposed to be hidden. Direct link to the package shows the latest version and does not list the earlier versions. So, the issue is with the search only.

[ewdurbin]

Original comment by Paddy Ganut (Bitbucket: paddy_ganut, GitHub: Unknown):

---

This is scrambling my search results (pi3d) and seems like a very serious issue. Do any of the site maintainers have any ideas what might be causing this?

PS If it helps any relevant dev. My package seemed to be correctly found as at v2.7 on 2015/08/14 but was acting up after v2.8 on 2015/11/07 It may not be relevant but there was a change to the indexing system by @dstufft in between, see commit 189386d It looks like a more complicated SQL but I've not really dug into it.

[ewdurbin]

Original comment by Anton Dries (Bitbucket: antondries, GitHub: Unknown):

---

I have the same problem with one of my packages (problog). Only old versions appear in the search, but pip install does find the latest version.

[farrokhi]

Same problem with dnsdiag package

[nickjacobson]

For https://pypi.python.org/pypi/testresources package the PyPI search turns up 2 old versions (0.2.7 and 1.0.0) instead of the newest, 2.0.1

[ewdurbin]

want to be clear that the pypi maintainers are aware and motivated to work on resolving these concerns. there have just been many more pressing concerns in the maintenance of PyPI and development of the next generation codebase warehouse

[divad]

Is there a likely ETA for fixing the search and similar issues, or an ETA for warehouse to replace the existing pypi? I don't think many people know just how broken pypi is, despite it being vitally important to so many projects and services and underpins so much of python!

[icemac]

What about already using https://pypi.io (aka warehouse)? Its index seems to be complete and correct. For many parts (aka searching a package) it should be sufficient.

[farrokhi]

@icemac how to instruct pip to use this as default?

[icemac]

@farrokhi: Why do you want to use https://pypi.io with pip? I thought this issue is about the web search on http://pypi.python.org.

[divad]

Its about both, surely... (the pip search is broken too...)

[farrokhi]

@icemac they use the same backend afaik

[icemac]

It seems that there was an update in the search index lately. Yesterday I was able to find the current version of my package named toll using all three searches. (No older versions showed up.) This was not the case before: It did not appear at all.

[ewdurbin]

Search has been patched up on PyPI. I'm triaging search related issues right now and most of the issues flagged in this thread have been resolved.

Please open a new issue with any ongoing search related bugs.