The summary (title) means something to me technically – there is a way I want to multiplex the python-use settings so a system can be easily switched from python-kit/3.4-prime to python-kit/3.6-prime, for example. This involves updating merge_utils.py to generate different python-use settings for different combos of python – and store them in the other kits' profiles/ directories (core, net, xorg, for example,) and having epro pick up these settings for each kit based on the activated branch of python-kit, as they will not activate without /etc/portage/make.profile/parent pointing to them explicitly. Totally technically feasible and should work with no issues. This will de-couple python-kit from the other kits and vice versa.