Thanks for the report. I reverted the commit that caused this in https://github.com/pypa/warehouse/pull/4015, however it might take a bit for this to get deployed to PyPI because there's currently a pretty long backlog in Travis due to all the PyPA development happening during the sprints.
D. On Wed, May 16, 2018 at 4:28 PM, Alex Becker <alcubec...@gmail.com> wrote: > In the last hour I started observing the following loop: > > https://pypi.org/pypi/nonexistant-package/json -> > https://pypi.org/pypi/nonexistant-package/json/ -> > https://pypi.org/pypi/nonexistant-package/json > > This is breaking pipenv package resolution for us, since we use 2 different > indices and it checks for a 404 from PyPI before going on to the second one. > I assume any pipenv or pip user relying on multiple indices is currently > unable to resolve packages.