SUMMARY Debian unstable and Ubuntu 20.04 proposed repo have a build of boost where python2 build/support is dropped. kig then fails to find BoostPython on configure, even though pythonboost is correctly installed. In the stable release repos where boost has python2 support and the pythonboost meta package pulls in python2 and python3, boost is found with the message: Found BoostPython: /usr/lib/x86_64-linux-gnu/libpython2.7.so;/usr/lib/x86_64-linux-gnu/libboost_python.so
If I understand correctly you are reporting that BoostPython is not found when all you have is Python 3, right? If that is the case, I believe it is by design since the Python scripting interface has not been adapted to Python 3. This should happen now because of the Python 2 EOL.
Not sure if there is more Python usage in Kig, but pykig was recently ported to Python3, see https://phabricator.kde.org/D25982
(In reply to Christoph Feck from comment #2) > Not sure if there is more Python usage in Kig, There is. > but pykig was recently ported > to Python3, see https://phabricator.kde.org/D25982 Right, and I believe the reporter may think this meant Kig now supports Python 3.
No, it was this commit in the scripting dir that must have made me think it was or should supported. https://cgit.kde.org/kig.git/commit/scripting?h=release/19.12&id=c0aa768f28219ce8b3c275a6d13ad69757e3c7af "Try to fix Python 3 build" Especially as that scripting dir only included by if(BoostPython_FOUND) add_subdirectory( scripting ) add_definitions(-DKIG_ENABLE_PYTHON_SCRIPTING) endif(BoostPython_FOUND)