[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Ned Deily added the comment: David, I think we are not going to change the Current symlink behavior at this point so we might as well close this issue. We may decide to address the need to pick which version to link with in a different manner later. -- resolution: -> wont fix stage:

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

R. David Murray added the comment: Ned, can this issue be closed or is there still something to discuss here? -- nosy: +r.david.murray ___ Python tracker ___

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Ronald Oussoren added the comment: There is a python3.3 in .../Python.framework/Versions/3.3/lib because .../Python.framework/Versions/3.3 is basicly a regular unix install with some trivial changes (in particular, there is a Python shared library in the root of the tree, there is a Python.app

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Gavan Schneider added the comment: 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

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Ronald Oussoren added the comment: Linking with "-framework Python" is always a bad idea because you have no control over which version of Python you link with other than by changing global system state (the Current link). Also: include files aren't included using the framework conventions (e.

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Gavan Schneider added the comment: Appreciate the comment about potential problems with mixed installations of python3 and python2. And note that along these lines there is no attempt by the installer to symlink python -> python3 (which could have nasty side effects if the full path was not sp

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Ned Deily added the comment: That behavior of the OS X installer is by design. Currently, the "Current" link is only set for Python 2 installations, not Python 3 ones. While that may have made sense in the early days of Python 3 (assuming there would be mixed installations of both Python 3 an

[issue18117] Missing symlink:Current after Mac OS X 3.3.2 package installation

Changes by Gavan Schneider : -- title: Missing symlink:Currnet after Mac OS X 3.3.2 package installation -> Missing symlink:Current after Mac OS X 3.3.2 package installation ___ Python tracker