On 9 May 2014 21:55, Paul Moore firstname.lastname@example.org wrote:
On 9 May 2014 12:44, Donald Stufft email@example.com wrote:
I think it's important to point out that one of
the driving factors that caused
me to finally push for changes and what lead to PEP438 being created was that
Mercurial's external hosted was being extremely flaky. I can't remember the
exact details but I want to say that over the span of a week or two I was
getting massive numbers of users complaining that
pip install Mercurial
was suddenly failing. This isn't to knock on the Mercurial folks or anything
but to simply point out that these problems aren't things that just happen to
(under|un)maintained software nor are they hypothetical. This PEP was born of
the frustration that was being relayed to me by end users of PyPI/pip.
So now "pip install Mercurial" always fails? And adding a flag allows it to work as well as before, but no better? How did that fix the issue? Seriously - I'm missing something here.
Mercurial downloads are now available directly from PyPI.
-- Nick Coghlan | firstname.lastname@example.org | Brisbane, Australia