The package unconditionally imports unittest2. I think that shouldn't be necessary in py2.7/3.2+.
If that is the case, then why does the virtual/python-unittest2 ebuild support those python versions? PYTHON_COMPAT=( python{2_5,2_6,2_7,3_1,3_2,3_3} pypy{1_9,2_0} )
Think I fixed it by changing the virtual/python-unittest2 to virtual/python-unittest2[${PYTHON_USEDEP}] Let me know if it's still broken :D
This bug is not about the dependencies, but about that actual installed code.
Sorry, I mean the test suite, not the installed code. See tests/utils.py.
(In reply to comment #1) > If that is the case, then why does the virtual/python-unittest2 ebuild > support those python versions? > > PYTHON_COMPAT=( python{2_5,2_6,2_7,3_1,3_2,3_3} pypy{1_9,2_0} ) Because we migrated all the packages prematurely to it and don't want random failures ;).
I'm going to close this, as it is using [${PYTHON_USEDEP}] and will be fixed when the virtual is fixed.