Re: Deprecate External Links

On Thu, Feb 28, 2013 at 7:00 PM, holger krekel <[email protected]> wrote:
> To summarize, having pip/easy_install report red warnings and requiring
> to pass a "--htmlscrape=PROJ1,PROJ2" option or so is a good way to
> communicate, removing the ability is not, at this point.

+1

I'm a fan of updating the client side tools (both upload and download)
to complain if files are not hosted on PyPI, and perhaps even
requiring switches or configuration settings to say "yes, external
downloads are OK for projects X, Y, and Z").

I'm *not* a fan of changing the way PyPI handles external links,
except perhaps for some of the suggestions PJE made about cleaning up
some aspects of what PyPI chooses to publish for old releases.

I'd prefer to leave the "you can't do it any more" step for the next
generation secure metadata distribution infrastructure (so the
installation tools will be able to fall back to the legacy
infrastructure for projects that haven't updated yet).

Cheers,
Nick.

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia