Display more information on non-200 status codes from package indexes

[alex]

As discussed pypa/packaging-problems#130 (comment)

More information should be shown when pip install gets a 4xx response from PyPI. Right now info is shown with -v, but it should be shown by default.

[njsmith]

I guess this may apply to 5xx errors as well.

[pradyunsg]

@pfmoore Do you think we can fit this into a 10.0 release or should let it wait?

[pfmoore]

As there's currently no PR for it, I'd rather let it wait. At this point, I'm really only looking to merge completed PRs and fixes for release blockers.

If you feel it's important enough, and can get a PR written and passing tests in the next day or so, I'd consider it. But it'd have to be a pretty small change. My number 1 priority at the moment is to look at #5085.

[alex]

The only short term reason this would be important is related to the TLS brownout for warehouse, but frankly that's going smoothly enough that I don't think this needs to be a priority.

…

On Sun, Mar 25, 2018 at 12:01 PM, Paul Moore ***@***.***> wrote: As there's currently no PR for it, I'd rather let it wait. At this point, I'm really only looking to merge completed PRs and fixes for release blockers. If you feel it's important enough, and can get a PR written and passing tests in the next day or so, I'd consider it. But it'd have to be a pretty small change. My number 1 priority at the moment is to look at #5085 <#5085>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAADBARhsaZx-F3qGHQdgt3OtBMSjbkKks5th79FgaJpZM4S48Ky> .

-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6

[edmorley]

The only short term reason this would be important is related to the TLS brownout for warehouse

Also the users affected would first have to update to pip 10.x to pick up this fix, at which point they'd no longer get the error anyway. Fixing this issue would be useful for future brownouts and other infrastructure issues however :-)