[ebuild U ] dev-python/bottleneck-1.0.0 [0.8.0] PYTHON_TARGETS="python2_7 python3_4 (-python3_5) (-python3_6)" python -c "from bottleneck.src.template.template import make_pyx; make_pyx();" Traceback (most recent call last): File "<string>", line 1, in <module> File "/var/tmp/portage/dev-python/bottleneck-1.0.0/work/Bottleneck-1.0.0/bottleneck/__init__.py", line 3, in <module> from . import slow File "/var/tmp/portage/dev-python/bottleneck-1.0.0/work/Bottleneck-1.0.0/bottleneck/slow/__init__.py", line 1, in <module> from bottleneck.slow.reduce import * File "/var/tmp/portage/dev-python/bottleneck-1.0.0/work/Bottleneck-1.0.0/bottleneck/slow/reduce.py", line 2, in <module> import numpy as np ImportError: No module named 'numpy' make: *** [Makefile:23: pyx] Error 1
Created attachment 499188 [details] build.log
Created attachment 499190 [details] emerge --info
I confirm the issue. This happens with the recently stabilized python-3.5. bottleneck-1.2.0 (see bug #614332) and bottleneck-1.2.1 compile just fine, mere upgrade of numpy to 1.13.3 caused by revbump of bottleneck (I am mostly on stable) is not enough.
(In reply to Alexander Bezrukov from comment #3) > I confirm the issue. This happens with the recently stabilized python-3.5. > bottleneck-1.2.0 (see bug #614332) and bottleneck-1.2.1 compile just fine, > mere upgrade of numpy to 1.13.3 caused by revbump of bottleneck (I am mostly > on stable) is not enough. I created /usr/local/portage/dev-python/bottleneck with bottleneck-1.2.0.ebuild. But 'emerge -v1 bottleneck' continues to install bottleneck-1.0.0 due to a dependency of pandas-0.20.3: root@lynx:/usr/local/portage/dev-python/bottleneck(93)# emerge -pv1 bottleneck These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-python/bottleneck-1.0.0::local [1.0.0::gentoo] PYTHON_TARGETS="python2_7 python3_4 python3_5* -python3_6" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-python/bottleneck:0 (dev-python/bottleneck-1.2.0:0/0::local, ebuild scheduled for merge) conflicts with dev-python/bottleneck[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/pandas-0.20.3:0/0::gentoo, installed) Any hint is appreciated.
(In reply to Juergen Rose from comment #4) > (In reply to Alexander Bezrukov from comment #3) > > I confirm the issue. This happens with the recently stabilized python-3.5. > > bottleneck-1.2.0 (see bug #614332) and bottleneck-1.2.1 compile just fine, ... > I created /usr/local/portage/dev-python/bottleneck with > bottleneck-1.2.0.ebuild. > But 'emerge -v1 bottleneck' continues to install bottleneck-1.0.0 due to a > dependency of pandas-0.20.3: ... > WARNING: One or more updates/rebuilds have been skipped due to a dependency > conflict: > > dev-python/bottleneck:0 > > (dev-python/bottleneck-1.2.0:0/0::local, ebuild scheduled for merge) > conflicts with > > dev-python/bottleneck[python_targets_python2_7(-),python_targets_python3_4(- > ),-python_single_target_python2_7(-),-python_single_target_python3_4(-),- > python_single_target_python3_5(-),-python_single_target_python3_6(-)] > required by (dev-python/pandas-0.20.3:0/0::gentoo, installed) ... BTW. pandas-0.21.0 is out.
After installing pandas-0.21.0 the issue disappeared.
Any news about the version bump?
I had the same problem. I checked eselect python and it had 3.4 set. Performing eselect set 3.5 fixed my problem.
(In reply to mark.kosmowski from comment #8) > I had the same problem. I checked eselect python and it had 3.4 set. > Performing eselect set 3.5 fixed my problem. I confirm this, it works for me now after eselecting the most recent versions of Python. Thank you!
Please don't use this bug for local overlay dependency resolution help or talk about version bump.
*** Bug 650688 has been marked as a duplicate of this bug. ***
This issue also pops up during python:3.6 update (the update itself caused the rebuild of the package).
(In reply to Till Schäfer from comment #12) > This issue also pops up during python:3.6 update (the update itself caused > the rebuild of the package). I confirm. Same problem here.
(In reply to Silvio from comment #13) > (In reply to Till Schäfer from comment #12) > > This issue also pops up during python:3.6 update (the update itself caused > > the rebuild of the package). > > I confirm. Same problem here. As in the past it is necessary to do: eselect python 3.6 after that it compiles without problems.
