So, now that 2.6 is gone, how about killing 3.2? 3.3 is the default nowadays, 3.4 is getting neat, we should expect 3.5 soon. We shouldn't also expect any more 3.2 releases: > Python 3.2.5 was released on May 15th, 2013. This release fixes a few regressions found in Python 3.2.4, and is planned to be the final 3.2 series bugfix release. What do you think?
$ gpy-upgrade-impl python3_2 python3_3 app-editors/retext:0 dev-python/Yamlog:0 dev-python/astng:0 dev-python/backports-lzma:0 dev-python/beaker:0 dev-python/execnet:0 dev-python/misaka:0 dev-python/mox3:0 dev-python/python-ldap:0 dev-python/pyxattr:0 dev-util/eric:5 net-misc/livestreamer:0
Sounds about right to me.
I think we can ignore Yamlog since it is dead and its only revdep is py2-only.
And the flag is masked now.
*** Bug 522456 has been marked as a duplicate of this bug. ***
Jeroen marked #522456 duplicate, but it actually isn't: please consider *unmasking* python_targets_python3_2 for dev-python/setuptools. The explanation can be found in the linked bug.
python3.2 has been moved to the python overlay https://github.com/gentoo/python/commit/63a2d3dcab039f0a4b0a3d4858a6540f2b3f24c0 Is there anything left to do here?
