Use this bug to track stable requests for packages where python3_4 has been added to PYTHON_COMPAT.
@idella4: Could you please properly assign bugs and leave CC'ing arch teams to the respective maintainers of those packages?
Real work remaining: Bug 530294 - dev-python/pyopenssl-0.14 and co. stable request Remaining arches: sparc Bug 530470 - dev-python/gmpy-2.0.4 stable request Remaining arches: amd64 Bug 530570 - =dev-python/pypax-0.9.0 =sys-apps/elfix-0.9.0-r1: stable request Remaining arches: sparc Bug 530572 - dev-python/pyquery-1.2.9 stable request Remaining arches: sparc Bug 530586 - dev-python/python-sqlparse-0.1.13 stable request Remaining arches: ia64, sparc Bug 530600 - dev-python/sqlalchemy-{0.7.10,0.9.8} dev-python/sqlalchemy-migrate-{0.7.2-r1,0.9.2} stable request (see comment #6 for full list) Remaining arches: ia64, sparc Bug 525934 - dev-python/sqlalchemy-migrate-0.9.2 keyword request Remaining arches: ia64, sparc Bug 525562 - =dev-python/python-sqlparse-0.1.13 =dev-python/pytest-cov-1.6 =dev-python/cov-core-1.7 keyword request Remaining arches: ia64, sparc Bug 530674 - net-im/pidgin-2.10.11 stable request Remaining arches: alpha, ia64, sparc Bug 530998 - net-irc/irssi-otr-1.0.0 stable request Remaining arches: amd64 Bug 545870 - dev-util/cmake-3.2.2 stable request Remaining arches: arm64, arm, ia64, ppc, sparc Bug 550808 - dev-python/pyftpdlib-1.4.0 stable request Remaining arches: amd64, arm, hppa, ia64, ppc64, ppc, sparc, x86 In other words, amd64 has 3 more bugs, x86 has one more bug, and other more-maintained arches are in the same range. Perhaps we should actually open up the stabilization at this point? Let's not wait for the slowest arch...
(In reply to Dirkjan Ochtman from comment #2) [...] > In other words, amd64 has 3 more bugs, x86 has one more bug, and other > more-maintained arches are in the same range. Perhaps we should actually > open up the stabilization at this point? Let's not wait for the slowest > arch... python-3.4 was stabilized long time ago... the pending task is to change profiles default to use 3.4 instead of 3.3
Ah, sorry. So is it true that that task is waiting for dependencies in this bug?
Yes... well, months ago situation was much worse and there were tons of packages that weren't supporting python 3.4 in stable tree