<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Jan 2017, at 14:24, Donald Stufft <<a href="mailto:donald@stufft.io" class="">donald@stufft.io</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="">[…] Past that, macOS is going to be the</div><div class="">largest casualty since their system Python does not support TLSv1.2 yet in any</div><div class="">version of their OS.</div></div></div></div></blockquote><div><br class=""></div>Not just the system Python on OSX, this also affects all <a href="http://Python.org" class="">Python.org</a> installers for OSX except 3.6. The 3.6 installer is the first one that doesn’t use the system installation of OpenSSL. Annoyingly with OpenSSL on OSX you have to options: either use an up-to-date release or have OpenSSL use the system CA trust store, but not both. Sigh…</div><div><br class=""></div><div>I have no idea how may users use the <a href="http://Python.org" class="">Python.org</a> installers on OSX, but this has the potential to affect a largish number of users on OSX including newbies (but far from all users on OSX, there’s also a sizeable population using Homebrew or Anaconda).</div><div><br class=""></div><div>Ronald</div></body></html>