@hroncok @torsava @gordonmessmer @Conan-Kudo (apologies to those I'm sure I
missed, feel free to tag more)
We've talked and talked and talked about this in way too many PR's: PR's
related to Python and other "language SIG" material linger on and on because we
don't know what to do with them and who's "authorative" on accepting a change
and whatnot. Not to mention the changes themselves. So sometime last year I
declared that we'll be pruning out the remaining language-specific bits out of
rpm , and that Python being the perfect candidate to start with because there's
a vibrant community that is handling this stuff and will be better off without
people like me standing cluelessly in the way. Time to make it so. I've been
hoping for some clear-cut point where we have no open PR's on this content, but
we have a couple of PR's that have been lingering on for quite some time now
(#1014, #1546), and we're closing in on that next release rapidly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1607#issuecomment-808188414
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
