Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for saslwrapper's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to saslwrapper. If you need anything from us, or something is unclear, please mention it here. Thank you.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Unless anyone else chimes in on this bug, I think it is time to let the saslwrapper package die. As far as I can find, it only existed inside the qpid 0.16 source distribution. When qpid was split up into various separate git trees for its 1.0+ rewrite, the saslwrapper code seems to have disappeared. I certainly don't have the time to maintain adopt it myself and update it for Python 3. In the meantime, there is a newer and better-maintained variation on the same theme here (not packaged in Fedora currently): https://github.com/cloudera/python-sasl and I see that there is also a pure Python implementation of the same thing ready to be added to Fedora in bug 1651849.
From the Python point of view, it is enough to just disable python2- subpackage. But of course, it's completely up to you.
Ohh yes, you mean because there is the Ruby bindings in there too. Hmm, I forgot about those. I suppose as long as the Ruby bits still compile I am fine to keep them, even though I don't actually use them and probably can't do any actual maintenance on them. So I will take out all the Python bindings for Fedora 31+ and just leave the Ruby bits as is, for the time being.
Oh... I just realised that python-qpid still actually depends on this. Now I'm confused... How does qpid upstream expect this to work, if they don't even have saslwrapper sources anymore? Or are they hidden somewhere that I couldn't find? But it seems qpid itself is also not Python-3-ready either so...
You are right. Let's wait for a while until we get some reply in qpid's bug.
python-qpid will be probably orphaned next week because there is no reply in the linked bug.
python-qpid is orphaned and will be retired in ~4 weeks so we can remove Python binding then.
I think that you can remove Python 2 bits from this package.
Ḯ've prepared the change for you: https://src.fedoraproject.org/rpms/saslwrapper/pull-request/1
Thanks for the pull request. Sorry for being so slow.
The change was reverted, but I can't find any explanation why. Please remove the python2-saslwrapper package again.
The change was reverted in https://src.fedoraproject.org/rpms/saslwrapper/c/ee7aeee5b795405105c50a5186de3cdfe5ab8cd0?branch=master Irina, what was the reason?
It seems the revert was done to fix a FTBFS: https://koji.fedoraproject.org/koji/taskinfo?taskID=41322039 checking for python... no checking for python2... no checking for python3... no checking for python3.9... no checking for python3.8... no checking for python3.7... no checking for python3.6... no checking for python3.5... no checking for python3.4... no checking for python3.3... no checking for python3.2... no checking for python3.1... no checking for python3.0... no checking for python2.7... no checking for python2.6... no checking for python2.5... no checking for python2.4... no checking for python2.3... no checking for python2.2... no checking for python2.1... no checking for python2.0... no configure: error: no suitable Python interpreter found While before, there was python3 present in the buildroot: https://koji.fedoraproject.org/koji/taskinfo?taskID=38454678 checking for python... no checking for python2... no checking for python3... /usr/bin/python3 checking for python version... 3.8 I can try switching the subpackage to Python 3.
Nope, won't do. saslwrapper.cpp:4379:25: error: 'PyInt_AsUnsignedLongMask' was not declared in this scope; did you mean 'PyLong_AsUnsignedLongMask'? But we can revert the latest commit and add BuildRequires: python3
The FTBFS bug for this is: https://bugzilla.redhat.com/show_bug.cgi?id=1794465
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Meanwhile Irina has actually retired saslwrapper entirely, which is fine with me. This bug is therefore WONTFIX for Fedora 33+.
Yes, saslwrapper was retired.