python_select can break MacPorts builds

Ben Tompkins nbits.spoken at
Fri Feb 18 16:42:40 PST 2011

The recent thread about python_select reminds me that within the last 2-4 weeks I have had at least 2 installs fail due to an incompatibility between the version of python expected by a python script executed as part of the build, and the version selected (manually by me) via python_select. If your build fails due to a broken python script and you have python_select-ed a recent (probably 3.x) version of python, type:

     python_select python26-apple

and restart the build. This should fix the problem, especially if you were recently goaded (by a MacPorts post-install script) into installing and using python_select. Note that the errant build isn't necessarily going to shout out "Broken python script!" but you should be able to ascertain this from the log file mentioned in the output. 

It seems to me that it is the responsibility not of the end-user but of the author of the port file to cache, modify as necessary, and restore the python_select-ed version of python.   


More information about the macports-users mailing list