It has no reverse dependencies so there is no good reason to still have it. Blocking python2_7 cleanup in mercurial.
Mercurial supports of Python3 is quite new and may still have few bugs (like https://bz.mercurial-scm.org/show_bug.cgi?id=6356) So I prefer to keep it for now to allow users to fallback to python2 version in case of trouble.
Fine, but please note this creates py27 back pressure on dev-python/docutils - dev-python/pygments where the latest stable version (2.6.1) has dropped py27 support. Every docutils revdep therefore creates an emerge conflict manifesting as not being able to upgrade to pygments-2.6.1.
dev-python/pygments is only needed for test which are restricted for mercurial due to #608720.
(In reply to Cédric Krier from comment #3) > dev-python/pygments is only needed for test which are restricted for > mercurial due to #608720. Restricted tests do not take the dependency out of dep resolution, but I was talking about the dep chain via docutils anyway. This is unconditional in 9999 ebuild and equally unconditional in docutils, as said every docutils revdep with py27 is blocking this cleanup.
Done in commit aa5ff3a94b4a672ef36adfd2381e96245fa33204...