A lot of this is past my level but speaking from my level I just want packages to be consistent, i.e., if there is a symlink it should point to something (preferably useful) not dangle as is the case now.

Also I want an installed version to "look the same" no matter what version it might be. Specifically the version number should only occur once in the file tree. This then allows me to specify ***at the system level*** what I want when invoking (via a Current or similar link) my postgres and other build scripts, specifically so they don't need to be hand crafted just so they build against new new and latest install.

If I ever get to the stage where I am building to a specific version that's not the global selection I can do that by taking proper steps (but that's not what I usually want to do after installing a new version).

Continuing in the vein of one only mention of the version number in the package tree: why is there a python3.3 folder inside .../Pyton.framework/Versions/3.3/lib? Won't lib/Python3.4 stuff get put in its own Version?

As for the reluctance to rename the package for 3.4. Wont it be Python3 and the rename could just as logically be done for the current release:
  /Library/Frameworks/
    Python.framework/... # all the Pyton 2 stuff
    Python3.famework
      Versions
        3.3/...
        3.4/...
        Current -> 3.4
        ...

Finally there seems to be a convention with all the other installed packages for a "Current" symlink (note especially Tcl/Tk) to do something useful within their respective "Versions" folder. Is it too much to suggest that Python just follow this convention (albeit with the package name changed to pyton3 to prevent potential conflicts)?

Anyway, please excuse my drifting so far from a simple report of a broken and/or missing installer link :)

Regards
Gavan Schneider