python-any-r1 is mainly for packages where Python is only used at build time. The eselected Python is used and changing that version later should not matter. In the case of xmms2, it installs Python bindings and given that it only supports a single Python version, anything building against these bindings will need to ensure that the same Python version is used. I have an ebuild locally for AlbumThing that I haven't got around to adding to the tree. It's no longer maintained and I'd ideally need to fix a few things first. I still use it though and as it only supports Python 2.7, it needs to ensure that xmms2 has the same. That can only be done when python-single-r1 is used. The good news is it's a straight swap. :)
Right you are. Pushed as: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d6807c3ca787fd2279190b2d4f4fb764d14cfff7 Thank you!
