title: Differences between Framework and non-Framework builds of Python on Mac OS X
body: <h3>Question</h3>
  
  <p>What are the differences between a Framework build and a non-Framework build (i.e., standard UNIX build) of Python on Mac OS X? Also, what are the advantages and disadvantages of each?</p>
  
  <h3>Preliminary Research</h3>
  
  <p>Here is the information that I found prior to posting this question:</p>
  
  <ul>
  <li><a href="http://www.mail-archive.com/pythonmac-sig@python.org/msg08954.html" rel="noreferrer">[Pythonmac-SIG] Why is Framework build of Python needed</a>
  
  <ul>
  <li>B. Grainger: "I seem to recall that a Framework build of Python is needed if you want to do anything with the native Mac GUI. Is my understanding correct?"</li>
  <li>C. Barker: "Pretty much -- to access the Mac GUI, an app needs to be in a proper Mac application bundle. The Framework build supplies that."</li>
  </ul></li>
  <li><a href="http://developer.apple.com/mac/library/documentation/General/Conceptual/DevPedia-CocoaCore/Framework.html" rel="noreferrer">Apple Developer Connection: Framework Definition</a>
  
  <ul>
  <li>"A framework is a bundle (a structured directory) that contains a dynamic shared library along with associated resources, such as nib files, image files, and header files. When you develop an application, your project links to one or more frameworks. For example, iPhone application projects link by default to the Foundation, UIKit, and Core Graphics frameworks. Your code accesses the capabilities of a framework through the application programming interface (API), which is published by the framework through its header files. Because the library is dynamically shared, multiple applications can access the framework code and resources simultaneously. The system loads the code and resources of a framework into memory, as needed, and shares the one copy of a resource among all applications."</li>
  </ul></li>
  <li><a href="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WhatAreFrameworks.html#//apple_ref/doc/uid/20002303" rel="noreferrer">Framework Programming Guide: What are Frameworks?</a>
  
  <ul>
  <li>"Frameworks offer the following advantages over static-linked libraries and other types of dynamic shared libraries:
  
  <ul>
  <li>Frameworks group related, but separate, resources together. This grouping makes it easier to install, uninstall, and locate those resources.</li>
  <li>Frameworks can include a wider variety of resource types than libraries. For example, a framework can include any relevant header files and documentation.
  Multiple versions of a framework can be included in the same bundle. This makes it possible to be backward compatible with older programs.</li>
  <li>Only one copy of a framework’s read-only resources reside physically in-memory at any given time, regardless of how many processes are using those resources. This sharing of resources reduces the memory footprint of the system and helps improve performance."</li>
  </ul></li>
  </ul></li>
  </ul>
  
  <h3>Background</h3>
  
  <p>Prior to Mac OS X 10.6 Snow Leopard, I hadn't thought much about this, as I simply would download and install the <a href="http://www.python.org/download/" rel="noreferrer">Python 2.6.2 Mac Installer Disk Image</a>, which is a framework build, and go about my business using virtualenv, pip, etc. However, with the changes in Snow Leopard to 64-bit, gcc, etc., I've noticed some issues that have made me want to build/compile Python 2.6.2+ myself from source, which leads me to my question of the differences and advantages/disadvantages of building Python as a MacOSX|Darwin framework.</p>