Description of problem: Python3 has been marked in upstream as stable and should be included in the xapian-bindings package. Version-Release number of selected component (if applicable): Latest Additional info: Support can be added by %build export RUBY_LIB=%{ruby_vendorlibdir} export RUBY_LIB_ARCH=%{ruby_vendorarchdir} - %configure --with-python --with-ruby --with-tcl + %configure --with-python --with-python3 --with-ruby --with-tcl make %{?_smp_mflags} V=1 And appropriate changes in the files portions.
According to the upstream changelogs this is in the 1.3 dev releases: * README: Add note that 1.3.2 has Python 3 support, and that this will be in stable release 1.4.0. 1.3 has been in development for a long time, I only want to move to it when I know it's going to be stable. I also need to test it to ensure no regressions in apps that use it, we had issues when we moved from 1.0 to 1.2
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
I see stable 1.4.0 release is now out, will be investigating updating this soon. Need to ensure the API/ABI is compatible with 1.2.x and if not what the impact is so any details here would be useful.