Am 16.06.2010 00:38, schrieb Tarek Ziadé:
2010/6/16 "Martin v. Löwis"<mar...@v.loewis.de>:
What's important also, is to make sure z3c.pypimirror includes the
server-side work, so existing mirrors can be upgraded.
Not really. z3c.pypimirror has a completely different function.
It's a mirroring script for PyPI. Why do you say it has a completely
different function ?
a) it's a selective mirror (IIUC); a PEP 381 mirror should be complete
b) it's also a superset-mirror, mirroring stuff that actually *isn't* on
PyPI. This is not needed for PEP 381
c) it edits the simple index pages, thus breaking the page signature.
So it is really aimed at private mirrors (IIUC, that's also what it is
used for), whereas PEP 381 is about public mirrors.
Operators
providing one of the official PyPI mirrors should use pep381client instead.
Of course, if people absolutely want to, they could also put PEP 381 support
in z3c.pypimirror, but that may result in a significant rewrite.
What I had in mind was using pep381client within z3c.pypimirror.
Not sure how this would work - but you can certainly feel free to copy
any code that you find useful into z3c.pypimirror.
Regards,
Martin
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
