On Wed, Jun 16, 2010 at 1:37 PM, "Martin v. Löwis" <span dir="ltr"><<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
It is likely that some people will setup a mirror and then "forget" to take care<br>
about it. Like our buildbots really.<br>
</blockquote>
<br></div><br>
The same can happen to any infrastructure, though. Amazon may decide to change the setup, and then the automated update procedure would break.<br>
Of course, they would give advance notice - but then somebody would<br>
have to react to that advance notice.<br></blockquote><div><br>That's not very likely, and if something does change it will be extremely well announced and documented. Amazon is providing a commercial service lots of people rely on, their process is formalized and professionalized. And if Amazon makes mistakes they'll figure out how to avoid them next time, while mirror providers are a rotating crew that is unlikely to easily or reliably learn from past mistakes. If we actually understood each time PyPI broke and fixed it none of this would be a problem; I'm not blaming anyone for that, but it's also not going to change and adding lots of mirror systems just adds more systems with exactly the same management problems that our current system has.<br clear="all">
</div></div><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>