On Fri, Oct 5, 2012 at 6:29 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > Paul Moore <p.f.moore <at> gmail.com> writes: > >> Right, that's not going to be enough for me. I have a web page where >> files are hosted at >> http://my.domain/datastore/VARYING_ENCODED_ID/filename.tar.gz. The >> problem is that VARYING_ENCODED_ID changes regularly. It's possible to >> calculate it in code, but only based on the current date and the >> package name It really isn't worth asking why, but I'm stuck with >> it. >> >> I'd envisage a design consisting of independent "Locators", one for a >> local directory, one for PyPI using XMLRPC, one for PyPI's "simple" >> webpage interface (IMO, we need both PyPI types, as the simple >> interface generates a lot of useless web scraping - look at the simple >> page for lxml, for example...). Users could add locators for any >> custom stores as needed. I wrote a 30-minute proof of concept, which >> is at https://bitbucket.org/pmoore/tools/src/67b33c15efad/bin/Locator.py >> if you're interested. > > I'll take a look - it sounds like the sort of approach I would take, to have a > high level interface for locating distributions that allows enumeration of > distributions, means of fetching them etc., with the ability to slot > in implementations for unusual cases like yours.
Is this supposed to go into the stdlib? Simple reference implementations (wsgiref) fare better there than frameworks (distutils). The pluggable installer metaframework belongs on pypi. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
