Since the split of Python3, the OS X installer build scripts in the
four active source trees have diverged due to multiple edits at
different times such that most changes can no longer be easily
merged across branches without significant hand editing, even
though the scripts differ only trivially in functionality.

The attached patches for the 26, trunk(27), 31, and py3k(31) trees result in an identical build script across all four with execution
tests for the following python3 differences:
    1. Installer packages "PythonProfileChanges" and
       "PythonSystemFixes" default to "not selected for install"
    2. Include "--with-computed-gotos" on configure.
    3. Do not change Framework/Current link during install.

Also included is another patch which, if applied, would restore the change made to trunk in r77030 to change the default installation
state of the UNIX Tools Package from "selected" to "not selected",
thus by default not installing any symlinks in /usr/local/bin. 
It's not clear why this change should be made and only to trunk,
at that.  If it is applied, it should be accompanied by appropriate
NEWS and Installer README changes as it would affect how many users currently access python on OS X.

Also note that these patches effectively take care of backporting to py3k and 31 the most recent installer script changes that were made to 2.6 and trunk in support of 10.6 and the newer universal build options.

Does this still affect 2.6 then?

This does not need to be a release blocker for 2.6.5; it can safely be applied post-release.  The 2.6 version of the installer script has had the most attention paid to it since the most recent Python releases - and the only ones since OS X 10.6 was released - have been 2.6.x ones.  These patches make all four versions identical going forward and add the latest 2.6 fixes to the others.  It should be a release blocker for 3.1.2.

Barry: these patches affect 2.6, but can easily wait for 2.6.6: its basically sync-ing the OSX package-building infrastructure between the 4 active Python branches. This does not directly affect anything seen by users.

I applied the update in r79119. Thanks!