I would prefer that "python" by default means Python 3 ASAP (on all platforms if I had my way), and all packages requiring Python 2 should explicitly require Python 2, and use python2 binary. Whatever happens should be agreed on as a policy, clearly defining the intent of the community, and then we can evaluate the gaps. Then we can agree on strategies to bridge the gaps.
Maybe organize a hackathon at a PyCon to deal with the massive backlog of bugs and give the maintainers some code reviewed pull requests? There's a couple of PyCons between now and then, at least.
On Wed, Apr 19, 2017, 11:29 Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote:
>>>>> "CS" == Charalampos Stratakis <cstratak@xxxxxxxxxx> writes:
CS> I would argue here that it is more of maintenance burden, trying to
CS> keep a SPEC file synced between distros, than having a different
CS> SPEC for each branch.
You might argue that, and I've been arguing it for years, but in the end
the maintainer makes that decision.
CS> There are even SPECs that use suse macros in order to keep the same
CS> SPEC pretty much everywhere,
That is forbidden in Fedora.
CS> and while it might be an interesting work to do, I do not really see
CS> any advantages from the packager's POV.
Well, the "fedpkg switch-branch epel7; git merge master" workflow is
rather convenient. It's hard to argue against that.
- J<
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
