In both 2.6 and 2.7 Python plugins no longer work on the mac, at least not in more recent versions of OSX. Things crash during starting of the Python code.
First guess is that the problem is with libstdc++ versus libc++.
If I manually build an Ambulantplayer on 10.9 with libstdc++ and then put the resulting libamplugin_python into a 2.6 or 2.7 distribution things work again. Need to investigate further.
Here is the configure line I used to build Ambulant:
../configure --with-macfat --with-python --with-python-plugin --disable-dependency-tracking --without-xerces CC=clang CXX=clang++ CXXFLAGS=-stdlib=libstdc++ OBJCFLAGS=-stdlib=libstdc++
Analyzed the problem, and the culprit seems to be the use of MACOSX_DEPLOYMENT_TARGET=10.7 in combination with building with the 10.10 SDK. (May happen with other combinations too).
This causes the c++ compilers to use libstdc++ in stead of libc++.
This causes the resulting plugins not to work anymore.
Will first test with 2.7 nightly builds (upping minversion to 10.8). If it works we should keep 2.6 distribution for 10.7 and rebuild a 2.6.1 for 10.8 and higher.