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 pdfshuffler'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 pdfshuffler. 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.
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know.
> - 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?) Written in Python 2 and not ported (yet). pdfarranger is a replacement (-> https://bugzilla.redhat.com/show_bug.cgi?id=1711611)
Is the plan to package pdfarranger and retire pdfshuffler?
It wasn't my plan when packaging pdfarranger but in my opinion it's the right thing to do now. From email exchange with the pdfshuffler developer I would not expect any more updates, let alone python3 support. I don't know of any breaking changes in pdfarranger so it would be an ideal replacement. (The package is currently in updates-testing.) If you want to retire pdfshuffler I can do any of the following tasks: 1) Add provides + obsoletes for pdfshuffler to pdfarranger 2) Add a symlink for the pdfshuffler executable to pdfarranger 3) Replace pdfshuffler by pdfarranger in the comps [1] 4) Replace pdfshuffler by pdfarranger in the upstream monitoring [2] pdfarranger is my first packet so I'm happy about any input about what I should / shouldn't do. [1] https://pagure.io/fedora-comps/blob/master/f/comps-f32.xml.in#_941 [2] https://release-monitoring.org/project/6488/
Yes, please do, but for Fedora 32 only! I'd happily review a pull request for 1) 2)
Any news or plan here?
Pull request is ready for review: https://src.fedoraproject.org/rpms/pdfarranger/pull-request/1
https://src.fedoraproject.org/rpms/pdfshuffler/c/81620ff922e3b3c6488e49228b8194db5b6664c5?branch=master