On Tue, Jan 28, 2025 at 06:58:17PM +0100, Aurélien COUDERC wrote: > Le lundi 27 janvier 2025, 19:37:39 UTC+1 [email protected] a écrit : > > > > Please try to avoid explicit Python versions in Build-Depends, you > > > > should be able to build-depend on "libpython3-dev, python3" (or > > > > even-better: "libpython3-all-dev, python3-all") > > > > > > Kdevelop is and IDE and has specific requirements regarding python > > > versions. > > > The current version has the following in its CMakeLists.txt [1] : > > > find_package(Python3 3.4.3...<3.14 COMPONENTS Interpreter Development > > > REQUIRED) > > > > That sounds like it supports any default version between 3.4 and 3.14. > > _ and 3.14… excluded ! > > > Almost all Python packages are in a situation like that. They support a > > few older versions, and probably support future versions, but they don't > > know for sure, yet. > > I don’t agree that it’s the same thing to not know for sure yet, and to > explicitly state future versions are expected not to be OK in your build > system. > > In this case it means we have to upgrade kdevelop-python anyway for it to > build with python 3.14, and we will update the build dependencies accordingly > when time comes.
Currently it has: Depends: ..., python3.13,..., libpython3.14 The build log says: -- Found Python3: /usr/bin/python3 (found suitable version "3.14.7", required range is "3.4.3...<3.16") found components: Interpreter Development Development.Module Development.Embed What the package actually uses is 3.14, the 3.13 dependency is not even used. The package will just FTBFS when trying to build against a non-supported Python3 version (currently >= 3.16), which covers everything. > Happy hacking, cu Adrian
