Adding python3_10 to PYTHON_COMPAT in ebuilds using python-any-r1 can cause meson/python-exec to report warnings in some circumstances. > python-exec: EPYTHON value invalid (python3.10). I first encountered this updating some Cinnamon ebuilds using python-any-r1 and meson. I was also able to reproduce with other ebuilds such as x11-misc/xkeyboard-config. Though, interestingly, not every python-any-r1+meson ebuild exhibits this behavior. Presumably this is because dev-lang/python-exec[-conf] and meson don't have python3_10 in PYTHON_TARGETS. I'm also not sure what would happen in a configuration where dev-lang/python-exec[-conf] have python3_10 but meson does not. I'm not sure if this is the responsibility of the python eclasses, the meson eclass, or the ebuild itself. Reproducible: Always
Created attachment 760791 [details] xkeyboard-config build log > [ebuild R ] dev-lang/python-exec-conf-2.4.6:2::gentoo PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB > [ebuild R ] dev-lang/python-exec-2.4.8:2::gentoo USE="(native-symlinks) -test" PYTHON_TARGETS="(pypy3) (python3_8) (python3_9) (-python3_10)" 0 KiB > [ebuild R ] dev-util/meson-0.59.4::gentoo USE="(-test)" PYTHON_TARGETS="python3_9 -python3_8 (-python3_10)" 0 KiB > [ebuild R ] x11-misc/xkeyboard-config-2.34::gentoo 0 KiB
Can you show an example of an ebuild which triggers it too? Thank you!
I attached a build log for xkeyboard-config. Were you looking for something different?
(In reply to Matthew Turnbull from comment #3) > I attached a build log for xkeyboard-config. Were you looking for something > different? sorry, I'd assumed it was with a new version in the PR you're working on!
I think the real cause is that python3_10 flag is masked on dev-lang/python-exec. What's the value of ACCEPT_KEYWORDS? Please attach or paste your 'emerge --info'.
Created attachment 760863 [details] emerge --info output
Well, in my opinion the biggest problem here is that I've neglected to un-stable-mask python3_10 on python-exec. I've removed the stable masks now, so on next @world upgrade python-exec should be built with all flags and the error should disappear. Not sure if there's anything else we can do about it.
I rebuilt everything and the EPYTHON warning is no longer present. So I'll consider this fixed :) I wonder if this can be avoided in the future if python-any-r1 could somehow ignore any masked PYTHON_TARGETS. Maybe just turn the python-exec warning into a verbose debug - or only print it if no valid interpreter is found.
Well, normally this shouldn't ever happen because python-r1/python-single-r1 both enforce the respective USE flags on python-exec. Perhaps python-any-r1 should also dep on it.
