Am 09.10.2008 18:36 Uhr, Martin v. Löwis schrieb:
If there would be an easy way to replicate the PyPI backend (no idea
about the implementation - any RDBMS involved) then there are likely
volunteers taking over the resources for a mirror of the current backend.
I don't think a mirror would help. If the original system is down,
who would tell users to go to alternative locations?
zc.buildout supports this using the 'find-links' option. As said, the
primary focus is for zc.buildout users (means the complete Zope & Plone
world).
Please tell us how a distributed PyPI backend would look like..one
requirement would be that the software and database part (if any) have
to be in a good shape - the last time I tried the PyPI software I have
not had the best impression.
Again, I don't think that distribution improves anything - I rather
would expect that it introduces new problems.
We already maintain a internal mirror of PyPI for a while (just because
we have the need for having PyPI available _all_ the time for production
reasons). And it works out pretty well.
Andreas
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. & Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
email;internet:[EMAIL PROTECTED]
title:CEO
tel;work:+49-7071-793376
tel;fax:+49-7071-7936840
tel;home:+49-7071-793257
x-mozilla-html:FALSE
url:www.zopyx.com
version:2.1
end:vcard
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
