Please move PYTHON_COMPAT from eclass to ebuilds. Having it set in eclass breaks our tools.
(In reply to Michał Górny from comment #0) > Please move PYTHON_COMPAT from eclass to ebuilds. Having it set in eclass > breaks our tools. Define what tools break and how so.
gpy-showimpls and other impl-handling tools from app-portage/gpyutils. Since it can't run complete ebuild environment, it relies on being able to read PYTHON_COMPAT from .ebuild files. $ gpy-showimpls firefox www-client/firefox:0 52.2.0: S a 52.3.0: ~ a 55.0.2: ~ a vs for a package defining PYTHON_COMPAT correctly: $ gpy-showimpls llvm sys-devel/llvm:0 3.4.2-r100: ~ a # 2.7 3.5.2-r100: ~ a # 2.7 3.6.2-r100: ~ a # 2.7 3.7.1-r3: S s 2.7 3.8.1-r2: ~ s # 2.7 3.9.1-r1: S s 2.7 sys-devel/llvm:4 4.0.1: ~ a 2.7 sys-devel/llvm:5 5.0.9999: a 2.7 sys-devel/llvm:6 9999: a 2.7