RIght I am fixing this right now. There's something we didn't talk about yet : since there will be other package indexes out there (not PyPI mirrors) that might have their own mirrors, we do need to provide somewhere the hostname that holds the mirrors IP for the client software to work the same way in all case.
That is, mirrors.pypi.python.org for PyPI, but maybe mirrors.packages.plone.org for another index. I'd go for a /mirror-hostname unique page at PyPI (and its mirrors) even if this page is unreachable when PyPI is down. This enforces that the other indexes also use the DNS technique, but I think it's fine Tarek On Sun, Mar 29, 2009 at 6:12 PM, "Martin v. Löwis" <[email protected]> wrote: > >> +A mirror has to be a hostname. For example: >> + >> +- http://pypi.my-company.com >> +- http://mirror-pypi.somewhere.org >> + > > That actually doesn't work - the mirrors have to be > IP addresses (and I need a commitment from the mirror > operator to not change it) > > Regards, > Martin > _______________________________________________ > Python-checkins mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-checkins > -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
