[Catalog-sig] V2 pre-PEP: transitioning to release file hosting on PYPI

holger krekel holger at merlinux.eu
Tue Mar 12 21:02:15 CET 2013


On Tue, Mar 12, 2013 at 20:59 +0100, M.-A. Lemburg wrote:
> On 12.03.2013 20:46, PJ Eby wrote:
> > On Tue, Mar 12, 2013 at 2:07 PM, M.-A. Lemburg <mal at egenix.com> wrote:
> >> Just a quick note (more later, if time permits)...
> >>
> >> On 12.03.2013 18:05, holger krekel wrote:
> >>> Hi Marc-Andre, all,
> >>>
> >>>>> - Prepare PYPI implementation to allow a per-project "hosting mode",
> >>>>>   effectively enabling or disabling external crawling.  When enabled
> >>>>>   nothing changes from the current situation of producing ``rel=download``
> >>>>>   and ``rel=homepage`` attributed links on ``simple/`` pages,
> >>>>>   causing installers to crawl those sites.
> >>>>>   When disabled, the attributions of links will change
> >>>>>   to ``rel=newdownload`` and ``rel=newhomepage`` causing installers to
> >>>>>   avoid crawling 3rd party sites.  Retaining the meta-information allows
> >>>>>   tools to still make use of the semantic information.
> >>>>
> >>>> Please start using versioned APIs for these things. The
> >>>> old style index should still be available under some
> >>>> URL, e.g. /simple-v1/ or /v1/simple/ or /1/simple/
> >>>
> >>> Not sure it is neccessary in this case.  I would think it makes
> >>> the implementation harder and it would probably break PEP381 (mirroring
> >>> infrastructure) as well.
> >>
> >> Here's what I meant:
> >>
> >> We publish the current implementation of the /simple/ index API
> >> under a new URL /simple-v1/, so that people that want to use
> >> the old API can continue to do so.
> > 
> > Do you know of anyone who's *actually* going to need/use this
> > alternate API.
> 
> 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 can't they just the XML-RPC API, the DOAP API, or
> > any other means of obtaining this information?
> 
> Those cannot easily be put on the CDN and
> would cause an unnecessary strain on the PyPI server.

The JSON API could be put on the CDN however.

> We could/should probably also make the PKG-INFO meta data file,
> plus some other static information such as upload/release dates
> (as RSS/Atom file) available on the /simple/ page to make this
> easier to use over the CDN.

That should go into a re-newed CDN PEP :)

holger

> 
> -- 
> Marc-Andre Lemburg
> eGenix.com
> 
> Professional Python Services directly from the Source  (#1, Mar 12 2013)
> >>> Python Projects, Consulting and Support ...   http://www.egenix.com/
> >>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
> >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
> ________________________________________________________________________
> 
> ::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::
> 
>    eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
>     D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
>            Registered at Amtsgericht Duesseldorf: HRB 46611
>                http://www.egenix.com/company/contact/
> 


More information about the Catalog-SIG mailing list