<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 28, 2013, at 2:57 AM, holger krekel <<a href="mailto:holger@merlinux.eu">holger@merlinux.eu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Tue, May 28, 2013 at 07:42 +0100, Paul Moore wrote:<br><blockquote type="cite">On 28 May 2013 02:53, Donald Stufft <<a href="mailto:donald@stufft.io">donald@stufft.io</a>> wrote:<br><br><blockquote type="cite">Figured it out.<br><br>Use HTTPS.<br><br></blockquote><br>Can I suggest that if the new CDN means that there are additional<br>restrictions on what is supported (I've used the XMLRPC API without https<br>in one-off scripts in the past) then the officially supported API should be<br>properly documented once and for all in a PEP, including some sort of<br>"what's new" or "rationale" section describing the various changes that<br>have occurred recently and their impact on user code?<br></blockquote><br>I second this. I am building tools that interact with PyPI and people<br>and customers are using them. I don't want to find a switch announced<br>which breaks them and then hear "sorry, that's the future now" without<br>this future being documented and discussed before the fact. The PyPI<br>infrastructure and its supported tool interactions today are as important as<br>evolving the language itself so PEPs are warranted. As with PEP438 i am<br>willing to help this process.<br><br><blockquote type="cite">I'm purely a casual user of the PyPI API and the discussion of these<br>changes haa mostly gone over my head. The one thing I've taken away from it<br>is that I may get problems if I just google for sample code to use. For<br>example, the above comment implies that<br><a href="http://wiki.python.org/moin/PyPIXmlRpc">http://wiki.python.org/moin/PyPIXmlRpc</a> (AIUI, the nearest to formal<br>documentation that the XMLRPC API has) is wrong (as it uses http).<br><br>I do appreciate all the work that is going on to improve the PyPI<br>infrastructure. I'm not saying the changes should be reverted, just that<br>the consequences should be clearly explained.<br></blockquote><br>I also appreciate Noah's and Donald's CDN work here, up to the point where <br>it breaks things for unclear reasons. Reasons which might very well<br>be valid, nevertheless!<br><br>best,<br>holger<br></blockquote></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>Moving to a CDN has been discussed before on either catalog-sig or distutils-sig (Can't recall which offhand).</div><div><br></div><div>Weekly status updates were posted to the infrastructure list as well as the communication between us and Fastly as we ironed out SSL issues.</div><div><br></div><div>The mirroring issue pre-invalidation was quickly corrected. We now invalidate and we are looking at a window that is at most a few seconds large.</div><div><br></div>-----------------</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Donald Stufft</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div>
</div>
<br></body></html>