https://bugzilla.redhat.com/show_bug.cgi?id=1014607 --- Comment #6 from Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> --- (In reply to Toshio Ernie Kuratomi from comment #5) > (In reply to Zbigniew Jędrzejewski-Szmek from comment #4) > > (In reply to Toshio Ernie Kuratomi from comment #3) > > > Note: python3 subpackages should only be added if upstream supports the > > > package on python3. > > Yes, the source seems to be 2/3 compatible. Since this is a really a one > > file package, making a separate source package seems like overkill. > > > The question is really about upstream support. It could be that the package > will stop functioning on python-3.4,5,6,7, etc. 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. > 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. -- 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