Please add your arch keyword to pygments. btw. All the tests pass for me.
Added ~sparc keyword because pygmentize utility appears to work and is a nice application. Also tests appear to run as they should. (with FEATURES=test or individually). I note, however, that at first attempt the build seemed to get caught in some sort of loop at the end of the first test (test_basic_api). I am not sure what to make of this; right now I'm just noting it as a curiosity --- if I run USE=doc FEATURES=test emerge pygments over and over, now and then it does hang in some sort of CPU loop after completing the first test but before reporting the results. I'll look at it as time permits; I have not seen anything similar elsewhere.
Marked ~hppa.
There is a bug in one of the lexers, which make the test suite take like forever to finish. It's not 100% reproducible b/c the input in the tests is randomly shuffled. I have tracked it down and filed a ticket upstream: http://dev.pocoo.org/projects/pygments/ticket/306 I am still asking for your keyword as it's just one of many supported lexers that has this problem.
~alpha/~ia64 done
Please also remove sys-apps/paludis python from package.use.mask once you keyword this package.
~ppc'd
~arm/~s390 done
~mips keyword added to current version of pygments due to numpy[test]->nose[doc]->sphinx->pygments dependency tree. We still have paludis[python] package.use.masked, so not quite yet done on this bug.
(In reply to comment #8) > ~mips keyword added to current version of pygments due to > numpy[test]->nose[doc]->sphinx->pygments dependency tree. > We still have paludis[python] package.use.masked, so not quite yet done on this > bug. Fixed.
