Re: V2 pre-PEP: transitioning to release file hosting on PYPI
Nick Coghlan <[email protected]> Wed, 13 Mar 2013 23:25:27 -0700
| Newsgroups | gmane.comp.python.catalog |
|---|---|
| Message-ID | <CADiSq7fJ-4kkww19zYsSuknKn-+t762U9y9pH1mg5nO-FmhVWQ@mail.gmail.com> |
On Wed, Mar 13, 2013 at 11:19 PM, Nick Coghlan <[email protected]> wrote: > On Wed, Mar 13, 2013 at 1:23 AM, M.-A. Lemburg <[email protected]> wrote: >> On 13.03.2013 07:28, Nick Coghlan wrote: >>> On Tue, Mar 12, 2013 at 12:59 PM, M.-A. Lemburg <[email protected]> wrote: >>>> I think we should establish a versioned API like that for PyPI >>>> to make progress easier. All major web APIs use versioning >>>> for this reason. >>> >>> Why set up versioning for something we want to phase out? There will >>> never be a simple-v3, so this is really overengineering the proposed >>> change. >> >> Who says that we want to phase out the /simple/ index ? > > I want to render it redundant, because it's a crazy way to distribute > completely inadequate metadata. Specifically, once we have the infrastructure in place to publish metadata v2.0 (or a suitable subset) to installation tools, the relatively impoverished contents of the simple index will be a legacy interface retained only to preserve the correct operation of existing tools. Regards, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia