Hello,

We have already basically deprecated Jython2.5 as something not really
worth maintaining unless some people actually use and request
supporting it. Therefore, all python-r1 ebuilds no longer are keyworded
for jython2.5.

Sadly, this means that python.eclass packages depending on python-r1
fail because of missing dependencies when users enable jython. Even
worse, if someone enables jython2_5 in PYTHON_TARGETS, the eclass
suggests enabling it in USE_PYTHON as well, effectively causing user to
enable the breakage.

I think we could:

1) disable reporting jython for USE_PYTHON<->PYTHON_TARGETS check,

2) disable jython2.5 completely in python.eclass and mask the
python_targets_jython2_5 flag.

but in case of 2) we should first make sure that no direct jython deps
are broken. As in, the java packages which actually use jython have all
necessary modules supported.

What are your thoughts?

-- 
Best regards,
Michał Górny