On Wed, Feb 27, 2013 at 13:00 -0500, Jesse Noller wrote: > > > 2. External links decrease the expected uptime for a particular set > > > of requirements. PyPI itself has become very stable, however > > > the same cannot be said for all of the hosts linked that the toolchain > > > processes. Each new host is an additional SPOF. > > > > > > Ex: I depend on PyPI and 10 other external packages, each > > > service has a 99% uptime so my expected uptime to > > > be able to install all my requirements would be ~89% (0.99 ** 11). > > > > > > > > There are many links which go to google, bitbucket or github - > > i doubt those services have worse availability than pypi.python.org > > (http://pypi.python.org), > > rather better. > > > > Also we would be loosing a lot of packages because i expect there to > > be a non-trivial amount of packages which will not be transferred to > > pypi.python.org (http://pypi.python.org) no matter how much people here > > think it's cool. > > > > Why not first have an a good infrastructure and capacity with > > pypi.python.org (http://pypi.python.org) so that people *want* to move > > their files there? > > > > best, > > holger > > > Ok, so we have that. What now?
I am not sure i understand. Just last week there were many installs going wrong - installs failing due to the http/https redirecting. I've got at least 3 occassions myself in the last months where i couldn't use pypi.python.org and i've heart similar things from other people. There is also the issue that it's not clear we could just put all packages from download locations to pypi.python.org due to sizing constraints - at least that is what i got from discussions here earlier. holger _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
