<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 20 Aug 2017, at 05:56, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" class="">ncoghlan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On 20 August 2017 at 05:27, Ian Hartley <span dir="ltr" class=""><<a href="mailto:iahartle@ucsd.edu" target="_blank" class="">iahartle@ucsd.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">Hi all,<div class=""><br class=""></div><div class="">I'm using PyCharm CE as my development environment, on a macintosh running mac OS 10.12.3.<br class=""></div></div></blockquote><div class=""><br class=""></div>Ah, that would explain why my intuitions were all wrong - I know how the Windows and *nix installation models work (and I believe the latter also covers homebrew on macOS), but not how the macOS framework installers work :)</div></div></div></div></blockquote><div><br class=""></div>FWIW: The framework installers on <a href="http://python.org" class="">python.org</a> work just like the other installers on upgrades: installing 3.6.2 on a system already running 3.6.1 replaces the 3.6.1 installation and doesn’t perform a side-by-side installation. The major differences w.r.t. a *nix installation are having an “odd” sys.prefix, and having different sys.prefix values for different feature releases.</div><div><br class=""></div><div>Ronald</div></body></html>