It seems like recently the default python3 interpreter was switched to python 3.4. Unfortunately the rhythmbox ebuild doesn't support it: !!! The ebuild selected to satisfy "media-sound/rhythmbox" has unmet requirements. - media-sound/rhythmbox-3.1::gentoo USE="cdr dbus libnotify libsecret python udev -daap -html -ipod -lirc -mtp -nsplugin -test -upnp-av -visualizer -webkit -zeitgeist" ABI_X86="64" PYTHON_SINGLE_TARGET="python3_3 -python3_2" PYTHON_TARGETS="-python3_3" The following REQUIRED_USE flag constraints are unsatisfied: python? ( python_targets_python3_3 ) The above constraints are a subset of the following complete expression: ipod? ( udev ) mtp? ( udev ) dbus? ( python ) webkit? ( python ) python? ( python_targets_python3_3 ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) emerge failed
The issue is not about python 3.4. It's about having a default on python 3.4 and not 3.3, it seems.
The issue is causing by switching the default from 3.3 to 3.4 without waiting for most packages to support 3.4 :S
should we reassign this to python team ?
(In reply to Gilles Dartiguelongue from comment #3) > should we reassign this to python team ? I can take care of this personally also :) (until this is the last blocker we have enough time to handle this)
This bug is still open as one of only a few remaining blockers for requesting python-3.4 stabilization. Is it still relevant?
Yes, but it's not a major blocker, I mean, once the default is changed in profiles, anyone can simply go ahead and switch the default on the listed packages too (simply moving the default from python3_3 to 3_4)
done
