Since v6.10 the Linux kernel depends on Python to build, at least if you need support for the drm/msm driver (CONFIG_DRM_MSM=y).
This is used to generate headers from source xml during build, not an unreasonable scenario. I much prefer Python over C or Perl or shell scripting for this type of file and string processing.
Yet I'm unsure what the stance for the Python build dependency is among the powers that be. It may have snug in under their radar.
Should I try it with drm/i915...?
@rburchell @jani I've been trying to defend the core. My multiple years removing perl dependencies from the build didn't get them out of the raid subsystem etc.
Python is in an especially terrible dependency these days because it's developed a single magic implementation policed by its userbase and forcibly expired every few months:
https://landley.net/notes-2024.html#09-04-2024
No ruby/mruby, php/ph7 gcc/llvm/tinycc allowed, only "you must upgrade to the current version of Microsoft (tm) Word to read this file".
re: the ongoing deterioration of Python... how do you get this wrong?
https://mastodon.social/@nf3xn/113129649501654985
So you have your own language specific package repository, separate from the distro repository, because you decided something perl did was a good idea. Sigh. Ok.
But either you are installing packages into the current user's home directory and having $LANGPATH find them, or your installer goes SUID root to install them globally. PICK ONE. If you run pip as root, why doesn't it install in ~root/.pip ?