From 9406d4bde72f72b8757f5c43158757efd6c4609d Mon Sep 17 00:00:00 2001 From: Virgil Dupras Date: Sat, 4 May 2019 16:51:44 -0400 Subject: [PATCH] dev-python/ipython: remove py2 hack All circular dependencies had py2 cleanly dropped, rendering the hack obsolete. Bug: https://bugs.gentoo.org/685040 Bug: https://bugs.gentoo.org/684962 Signed-off-by: Virgil Dupras Package-Manager: Portage-2.3.62, Repoman-2.3.11 --- dev-python/ipython/ipython-7.5.0.ebuild | 30 ++++++------------------- 1 file changed, 7 insertions(+), 23 deletions(-) diff --git a/dev-python/ipython/ipython-7.5.0.ebuild b/dev-python/ipython/ipython-7.5.0.ebuild index 2a20f1205ac3..75c58af6c00d 100644 --- a/dev-python/ipython/ipython-7.5.0.ebuild +++ b/dev-python/ipython/ipython-7.5.0.ebuild @@ -18,21 +18,6 @@ KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux" IUSE="doc examples matplotlib notebook nbconvert qt5 +smp test" RESTRICT="!test? ( test )" -# About "-python_targets_python2_7": -# The ipython stack is in a tricky transition to py3-only. It has many circular -# dependencies which causes a chicken-and-egg problem because for Portage to -# properly handle dependency resolution on a system with -# python_targets_python2_7 all members of the circular dependency must go -# py3-only at the same time. If they don't, the dependency that requires py2 -# will seek older ipython releases for resolution. This is why, for members -# of the circular dependency, we force -python_targets_python2_7. This way, the -# circle stays firmly in py3-only land. This only affects members of the -# circular dependency. Other dependencies can be on py2 without problem. -# -# This situation also require us to explicitly depend on transitive dependencies -# that are part of the circular dependecy so that we preserve "circle -# integrity". It's a bit ugly, but temporary. - CDEPEND=" dev-python/backcall[${PYTHON_USEDEP}] dev-python/decorator[${PYTHON_USEDEP}] @@ -43,17 +28,17 @@ CDEPEND="