#16933: RFE: Make Python 2.6 more Framework Friendly ------------------------------------+--------------------------------------- Reporter: mcalhoun@macports.org | Owner: blb@macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: python26 | ------------------------------------+--------------------------------------- Comment(by mcalhoun@macports.org): I am not sure that the lack of ${prefix}/lib and ${prefix}/include will be a major problem. Some ports are smart enough to ask python what to do.[[BR]] graphviz for example has the following in its configure script: {{{ PYTHON_PREFIX=`$PYTHON -c "import sys; print sys.prefix"` PYTHON_INCLUDES=-I$PYTHON_PREFIX/include/python$PYTHON_VERSION_SHORT PYTHON_LIBS="-L$PYTHON_PREFIX/lib$LIBPOSTFIX/python$PYTHON_VERSION_SHORT/config" PYTHON_INSTALL_DIR="`$PYTHON $srcdir/config/config_python.py archsitelib`" }}} This type of thing is actually one of the sources of the problem with python25, which was discussed in #16334.[[BR]] graphviz tried to install in the Framework library directory, but they had been made into soft links to ${prefix}/lib.[[BR]] MacPorts can't handle installation into links to directories. If a port does not ask python directly for the settings, I think that a couple of -I... and -L... might be all that is required. So far, boost, graphviz, and pdflib are non-PortGroup ports which work with the new python26 with minimal effort. -- Ticket URL: <http://trac.macports.org/ticket/16933#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS