Please stabilize.
Is there anything blocking this?
This makes automated testing a pain: dev-python/idna:0 (dev-python/idna-3.1:0/0::gentoo, ebuild scheduled for merge) USE="" PYTHON_TARGETS="python3_7 python3_8 python3_9 -pypy3" pulled in by =dev-python/idna-3.1 (Argument) (dev-python/idna-2.10-r1-1:0/0::gentoo, installed) USE="" PYTHON_TARGETS="python3_7 python3_8 python3_9 (-pypy3) -python3_6" pulled in by <dev-python/idna-3[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)] required by (dev-python/requests-2.25.1-r1-1:0/0::gentoo, installed) USE="-socks5 -test" PYTHON_TARGETS="python3_7 python3_8 python3_9 (-pypy3)" ^
amd64 arm arm64 hppa ppc ppc64 s390 sparc x86 (ALLARCHES) done all arches done
Err, no can see them.
*** Bug 783285 has been marked as a duplicate of this bug. ***
(In reply to Michał Górny from comment #4) > Err, no can see them. Hmm.
Yep, still not there. I would have committed them for you but I'm not sure if you actually tested the right version ;-).
amd64 arm arm64 hppa ppc ppc64 sparc x86 (ALLARCHES) done all arches done
(In reply to Sam James from comment #2) > This makes automated testing a pain: > > > dev-python/idna:0 > > (dev-python/idna-3.1:0/0::gentoo, ebuild scheduled for merge) USE="" > PYTHON_TARGETS="python3_7 python3_8 python3_9 -pypy3" pulled in by > =dev-python/idna-3.1 (Argument) > > (dev-python/idna-2.10-r1-1:0/0::gentoo, installed) USE="" > PYTHON_TARGETS="python3_7 python3_8 python3_9 (-pypy3) -python3_6" pulled in > by > > <dev-python/idna-3[python_targets_pypy3(-)?,python_targets_python3_7(-)?, > python_targets_python3_8(-)?,python_targets_python3_9(-)?,- > python_single_target_pypy3(-),-python_single_target_python3_7(-),- > python_single_target_python3_8(-),-python_single_target_python3_9(-)] > required by (dev-python/requests-2.25.1-r1-1:0/0::gentoo, installed) > USE="-socks5 -test" PYTHON_TARGETS="python3_7 python3_8 python3_9 (-pypy3)" > ^ I'm not doing automated testing, but I am seeing, for obvious reasons as per the dev-python/requests ebuild, the same block. Not sure that I know what the underlying issues are (or why this is not generally encountered as a problem) but I did come across the following discussion: https://github.com/psf/requests/issues/5710 in case that helps at all Thanks
The Problem above with dev-python/requests are this lines in the ebuild: RDEPEND=" >=dev-python/certifi-2017.4.17[${PYTHON_USEDEP}] >=dev-python/chardet-3.0.2[${PYTHON_USEDEP}] <dev-python/chardet-5[${PYTHON_USEDEP}] >>>>> >=dev-python/idna-2.5[${PYTHON_USEDEP}] >>>>> <dev-python/idna-3[${PYTHON_USEDEP}] <dev-python/urllib3-1.27[${PYTHON_USEDEP}] socks5? ( >=dev-python/PySocks-1.5.6[${PYTHON_USEDEP}] ) " and are also related to https://bugs.gentoo.org/787584
(In reply to Icebird2000 from comment #10) > The Problem above with dev-python/requests are this lines in the ebuild: > > RDEPEND=" > >=dev-python/certifi-2017.4.17[${PYTHON_USEDEP}] > >=dev-python/chardet-3.0.2[${PYTHON_USEDEP}] > <dev-python/chardet-5[${PYTHON_USEDEP}] > > >>>>> >=dev-python/idna-2.5[${PYTHON_USEDEP}] > >>>>> <dev-python/idna-3[${PYTHON_USEDEP}] > > <dev-python/urllib3-1.27[${PYTHON_USEDEP}] > socks5? ( >=dev-python/PySocks-1.5.6[${PYTHON_USEDEP}] ) > " > > and are also related to https://bugs.gentoo.org/787584 Yup, I understand where the block is coming from. The point (if I understand things correctly) is that >=idna-3.0 is blocked by dev-python/requests because, upstream, requests continues support for python 2.7. However, as python 2.7 is no longer supported in PYTHON_TARGETS on gentoo, perhaps continuing to block >=idna-3.0 in the requests ebuild is no longer necessary?
(In reply to Adrian Bassett from comment #11) > (In reply to Icebird2000 from comment #10) > > The Problem above with dev-python/requests are this lines in the ebuild: > > > > RDEPEND=" > > >=dev-python/certifi-2017.4.17[${PYTHON_USEDEP}] > > >=dev-python/chardet-3.0.2[${PYTHON_USEDEP}] > > <dev-python/chardet-5[${PYTHON_USEDEP}] > > > > >>>>> >=dev-python/idna-2.5[${PYTHON_USEDEP}] > > >>>>> <dev-python/idna-3[${PYTHON_USEDEP}] > > > > <dev-python/urllib3-1.27[${PYTHON_USEDEP}] > > socks5? ( >=dev-python/PySocks-1.5.6[${PYTHON_USEDEP}] ) > > " > > > > and are also related to https://bugs.gentoo.org/787584 > > Yup, I understand where the block is coming from. > > The point (if I understand things correctly) is that >=idna-3.0 is blocked > by dev-python/requests because, upstream, requests continues support for > python 2.7. > > However, as python 2.7 is no longer supported in PYTHON_TARGETS on gentoo, > perhaps continuing to block >=idna-3.0 in the requests ebuild is no longer > necessary? This has now been resolved - cf. https://bugs.gentoo.org/787584#c3