https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #10 from Pino Toscano <p...@kde.org> --- (In reply to Sven Brauch from comment #9) > Hi, I think ideally in this case you would have notified me that you needed > Python 3.11 support in Gear 22.12. I would have backported it there. While that is true, I think it would not be unreasonable to expect that, once a new Python version is released, it will start to flow into distros, and distro packagers will need to make sure all the Python-using packages (modules, plugins like kdev-python, etc) are compatible with it. > Still, I dunno. I made an explicit, conscious decision to not include the > patch in our tagged release because I knew it was risky, and it was just > shipped to users regardless, without me even knowing. That's odd to me. What I can tell you from my POV (not even with a DD hat, as non-kdevelop contributor) is that I don't find it easy to determine what you can "conscious decision": sometimes maintainer do not backport patches at all in stable branches, sometimes they do when requested, sometimes they do aggressively... and you don't know what's the actual case here, unless you really know each person involved. So please bear with people that are not part of the "kdevelop development group". Back to the actual situation here: 1) should I drop the extra bits of Python 3.10 support, even if there will be (hopefully soon) a fix for that coming? 2) should I drop the support for Python 3.11, since it is not in 22.12.x as "conscious decision"? -- You are receiving this mail because: You are watching all bug changes.
