https://bugzilla.redhat.com/show_bug.cgi?id=1014607 --- Comment #7 from Toshio Ernie Kuratomi <a.badger@xxxxxxxxx> --- (In reply to Zbigniew Jędrzejewski-Szmek from comment #6) > Experience seems to suggest otherwise: many packages are slow to get python > 3 support, but once it happens, they usually don't drop it. Looking at the > sources, it seems more likely that python 2 support will dropped, since it > is provided as compatibility imports. > I'm not sure I understand you but if I do then you are making incorrect assumptions. There are many packages which have added python3 support but when upstream makes updates the python2 versions are tested while the python3 versions are buggy and have to be patched by package maintainers and those packages sent upstream. > > If the jsmin upstream > > doesn't (at least) take patches to fix python3 problems then you'll be stuck > > generating fixes for the python3 problems yourself without upstream help. > > You'll have to carry patches in the Fedora package to fix the issues. At > > that point, you've really forked the software and are shipping something > > different from wat upstream provides. > I'm pretty sure that the work required to go through a second review for a > separate package trumps all work to support python 3 compatibility. then you would be wrong. Just take a look at some of our essential and problematic packages like python-docutils and python-nosetests where the python3 compatibility has held back updates for a week or more at a time both when they update and when Fedora updates the version of the python3 interpreter. The one-time pain of a second package and review is trivial compared to the ongoing maintenance of a package. Anyhow, the Packaging Guidelines specify that unless upstream supports building the python3 package not to build it as a subpackage of the python2 package. So someone should just find out if upstream supports this. If they do, then feel free to build it as a subpackage. If not, then do not. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review