------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0_libressl_20170909-193047 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 7.2.6.11 [icedtea-bin-7] 2) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 system-vm [2] icedtea-bin-8 emerge -qpv dev-python/rope [ebuild N ] dev-python/rope-0.10.7 USE="-doc" PYTHON_TARGETS="python2_7 python3_4 -python3_5 -python3_6"
Created attachment 495064 [details] emerge-info.txt
Created attachment 495066 [details] dev-python:rope-0.10.7:20170916-230810.log
Created attachment 495068 [details] emerge-history.txt
Created attachment 495070 [details] etc.portage.tbz2
I think this is what caused a faulty Python 3 installation of rope-0.10.7 for me. Many of its files were apparently missing after an upgrade from 0.9.4 and I got dependency errors in other code (spyder3). Re-emerging rope-0.10.7 fixed this. But it is useful to let you know that this has real-world impact.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e41b9fbae269bf891f55e3802f2dbacf064e974d commit e41b9fbae269bf891f55e3802f2dbacf064e974d Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2017-11-02 11:52:53 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2017-11-02 12:28:50 +0000 dev-python/rope: Add blocker on dev-python/rope_py3k Closes: https://bugs.gentoo.org/631264 dev-python/rope/rope-0.10.7.ebuild | 1 + 1 file changed, 1 insertion(+)
