It looks like the default python3 interpreter was recently bumped to 3.4. Unfortunately dev-libs/libpeas ebuild doesn't claim to support that version, which becomes problematic due to it being a dependency for other packages like app-editors/gedit, media-sound/rhythmbox etc.
Maybe 1.12.1 does? Also, how is it a problem that 3.4 might not yet be supported? Surely no ebuilds that depend on libpeas expect it to?
(In reply to Jeroen Roovers from comment #1) > Also, how is it a problem that 3.4 might not yet be supported? It forces gnome users to add over a dozen "foo/bar python_targets_python3_3" entries to their package.use file. And the list of these foo/bar entries needs to be determined experimentally by repeatedly running emerge world and looking at the errors portage prints.
And usually portage doesn't even resolve the issue and, then, cannot automatically unmask it. Apart of that, this affects more stuff than gnome, for example, I am also having problems with PyQT4 and others (still having blockers on my system). Shouldn't the default be switched back to 3.3 over 3.4 as there are still a lot of packages *in stable tree* that don't support 3.4?
Just to be clear, does anyone know of an actual compatibility issue here? Upstream makes a blanket claim to support "Python 3" without specifying the minor version; I couldn't find any reason to think that they consider 3.3 OK but 3.4 unsupported. It looks to me like the only reason that 3.4 isn't in PYTHON_COMPAT is because no one ever got around to updating the ebuild.
done
Should this be done for stable versions? I.e. dev-libs/libpeas-1.10.0 and app-editors/gedit-3.12.2 (for #530230).
The fixed libpeas version will go to stable soon... and there are many many more packages needing to be ported to 3.4 still apart of this one -> bug 530258
