On 26.11.2008 8:33 Uhr, Tarek Ziadé wrote:

On Wed, Nov 26, 2008 at 8:22 AM, Andreas Jung wrote:

...

Hi there,

in buildout I can define only one alternative index server using 'index = http://pypi.zopyx.com'. Now we are in the situation where we are running two internal index servers (one for our own internal packages and one PyPI mirror). Is there some reason for this limitation? I assume this is a limitation/feature coming from setuptools?

Yes it is. That is exactly where setuptools needs to evolve.

For the record: I have asked for that a few months ago, and Jim said he wanted to stick with setuptools.

So proposed a patch in setuptools to be able to merge several indexes, (see http://bugs.python.org/setuptools/issue32)

But it hasn't been reviewed yet.

I think this is a very helpful patch. We would appreciate it if the patch could make it into the next setuptools release asap. Andreas

On 26.11.2008 9:54 Uhr, Tarek Ziadé wrote:

On Wed, Nov 26, 2008 at 8:46 AM, Andreas Jung wrote:

...

On 26.11.2008 8:33 Uhr, Tarek Ziadé wrote:

...

On Wed, Nov 26, 2008 at 8:22 AM, Andreas Jung wrote:

...

Hi there,

in buildout I can define only one alternative index server using 'index = http://pypi.zopyx.com'. Now we are in the situation where we are running two internal index servers (one for our own internal packages and one PyPI mirror). Is there some reason for this limitation? I assume this is a limitation/feature coming from setuptools? Yes it is. That is exactly where setuptools needs to evolve.

For the record: I have asked for that a few months ago, and Jim said he wanted to stick with setuptools.

So proposed a patch in setuptools to be able to merge several indexes, (see http://bugs.python.org/setuptools/issue32)

But it hasn't been reviewed yet. I think this is a very helpful patch. We would appreciate it if the patch could make it into the next setuptools release asap.

I made an assumption to use -i but I don't know if it would be better to have a new argument for it. Besides, this index merging thing would be helpful for merging *different* sources

Merging is exactly our problem right now (I can get around with generating index pages manually right now...works but not really nice). Not sure where the problem is with the -i parameter. Either we can allow serveral -i options or just use something like: -i http://pypi.zopyx.com,http://pypi.foo.com

for mirrors, I think we need something specific : a fail-over mechanism over a list of mirrors for a given pypi-like server, with a "nearest mirror picked" feature (see my blob + pep 374 on python wiki)

Mirror selection is a different subject and not the problem here. Andreas

On 26.11.2008 11:04 Uhr, Tarek Ziadé wrote:

On Wed, Nov 26, 2008 at 10:09 AM, Andreas Jung wrote:

...

On 26.11.2008 9:54 Uhr, Tarek Ziadé wrote:

...

On Wed, Nov 26, 2008 at 8:46 AM, Andreas Jung wrote:

...

On 26.11.2008 8:33 Uhr, Tarek Ziadé wrote:

...

On Wed, Nov 26, 2008 at 8:22 AM, Andreas Jung wrote:

...

Hi there,

in buildout I can define only one alternative index server using 'index = http://pypi.zopyx.com'. Now we are in the situation where we are running two internal index servers (one for our own internal packages and one PyPI mirror). Is there some reason for this limitation? I assume this is a limitation/feature coming from setuptools? Yes it is. That is exactly where setuptools needs to evolve.

For the record: I have asked for that a few months ago, and Jim said he wanted to stick with setuptools.

So proposed a patch in setuptools to be able to merge several indexes, (see http://bugs.python.org/setuptools/issue32)

But it hasn't been reviewed yet. I think this is a very helpful patch. We would appreciate it if the patch could make it into the next setuptools release asap. I made an assumption to use -i but I don't know if it would be better to have a new argument for it. Besides, this index merging thing would be helpful for merging *different* sources Merging is exactly our problem right now (I can get around with generating index pages manually right now...works but not really nice).

Not sure where the problem is with the -i parameter. Either we can allow serveral -i options or just use something like:

-i http://pypi.zopyx.com,http://pypi.foo.com

well yes, that is how I implemented it, but I don't know if that is how Phillip Eby wants it.

...

...

for mirrors, I think we need something specific : a fail-over mechanism over a list of mirrors for a given pypi-like server, with a "nearest mirror picked" feature (see my blob + pep 374 on python wiki) Mirror selection is a different subject and not the problem here.

I am saying that because you don't want to merge a source and a mirror, so as long as http://pypi.zopyx.com != http://pypi.foo.com, it is OK.

Of course not. As said initially we are running a PyPI mirror and an egg server with our private packages that will never end up on PyPI. Andreas

Andreas Jung wrote:

...

Is there some reason adding find-links with your other indexes in doesn't work? It works for me in the same situation...

The index package for a complete PyPI mirror is pretty long (too long to be loaded and to be parsed).

Why do you need a complete mirror? Surely your index page only needs to list your private packages?

In addition we would have to update the index page for our internal egg server upon every change.

Well yeah, but you can just use Apache's file index or (as I do) a subversion http server for this...

right now but it sux. Using 'index' is appearently much cleaner and resource-friendly.

Really? Surely it still has to do just the same html processing, etc? Can someone please comment on this authoritatively? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk