On 05/09/2011 02:09 PM, Mathieu Leduc-Hamel wrote:

yes but with find-links i think you are forced to defined a specific link which point directly to the package, and the index option is where you can specify another pypi index.

am i right ?

Depends what you mean by "point directly to the package" - you give find-links a URL that contains HTML links to package tarballs, named appropriately (or with #egg= suffixes) to be recognizable as project+version. So it's pretty easy to use a webserver directory with directory indexes on and dump whatever sdists you want in there. But you're right that find-links isn't quite the same as using an alternative index, or multiple indexes, just in that the URL structures used for project/version lookups on a PyPI-compatible index have an inherent nesting. This only really matters if you're dealing with so many packages that dumping the sdists in a single directory becomes unwieldy. FWIW, pip supports both --find-links and multiple indexes (via --extra-index-url). Carl

Great, thanks Chris and Carl, but does it mean i can use the find-links in the same spirit of the index option ? i'll like to be able to point our buildout to our internal pypi instance and also other ones, that was the point of my question... On Wed, May 11, 2011 at 9:21 AM, Chris Withers <chris@simplistix.co.uk> wrote:

On 09/05/2011 20:09, Mathieu Leduc-Hamel wrote:

...

yes but with find-links i think you are forced to defined a specific link which point directly to the package, and the index option is where you can specify another pypi index.

am i right ?

Nope,

find-links can be an a folder on disk or an html page containing links, such as that served by Apache's indexes. Other things may work too, those are the two I've tried...

cheers,

Chris

-- Simplistix - Content Management, Batch Processing & Python Consulting           - http://www.simplistix.co.uk

-- Mathieu Leduc-Hamel

Hi Mathieu. To complexify Chris' unambiguous "YES!" slightly: On 05/11/2011 08:26 AM, Mathieu Leduc-Hamel wrote:

Great, thanks Chris and Carl, but does it mean i can use the find-links in the same spirit of the index option ?

In the same spirit, certainly. But the details of how you use it will be different, as I explained in my last message.

i'll like to be able to point our buildout to our internal pypi instance and also other ones, that was the point of my question...

Depends what you mean by "our internal pypi instance." If you already have a running instance of some software that emulates PyPI, including the specific layout of PyPI's project/version URLs, and you're tied to keeping that, you will not be able to just point find-links at that index. You would need something more like pip's --extra-index-url; I don't know if buildout has something like that or not. On the other hand, if by "our internal PyPI" you just mean that you have some sdist tarballs and you can put them on a webserver, then yes, just dump them all in a single web-served directory, turn indexes on, and point find-links at that URL, and that should meet your needs just as well. Carl

Hi Chris, On 05/11/2011 11:17 AM, Chris Withers wrote:

On 11/05/2011 17:02, Carl Meyer wrote:

...

Depends what you mean by "our internal pypi instance." If you already have a running instance of some software that emulates PyPI, including the specific layout of PyPI's project/version URLs, and you're tied to keeping that, you will not be able to just point find-links at that index.

Sure you would, as if this was the case, it would have the same 'simple' view that the real PyPI has, you'd just need to point find-links at that.

That doesn't actually work. The simple index is still one link away from the actual tarball links, and find-links doesn't spider across. I just tested with both easy_install and pip, and with either one, pointing find-links directly at the PyPI simple/ page does not work. You'd have to use e.g. --find-links http://pypi.python.org/simple/projectname when installing "projectname".

I'm not sure, but you might see find-links doing the insane setuptools spidering this, in which case, even non-simply links will be fine.

simple/ is irrelevant here, it would have to spider in either case. And it doesn't.

So, the short YES would have sufficed and been less confusing ;-)

Also wrong ;-) Carl