'ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly' #281

lcflorindo · 2019-11-29T12:41:45Z

Hi, I'm installing Bottleneck by fastai lib in a Suse 12 sp4 server, but had the error when building wheels for it.
It says that uses PEP517 and cannot be installed directly. Funny thing is that I had it installed on my (base) but when I move to my app env it just jams on the error.
There is a way to solve it? Thanks in advance!

(pycamlar) (base) filholf@127.0.0.1:~/pycamlar> pip install --no-cache-dir Bottleneck
Collecting Bottleneck
  Downloading https://files.pythonhosted.org/packages/62/d0/55bbb49f4fade3497de2399af70ec0a06e432c786b8623c878b11e90d456/Bottleneck-1.3.1.tar.gz (88kB)
     |████████████████████████████████| 92kB 1.1MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Requirement already satisfied: numpy in ./pycamlar/lib/python3.7/site-packages (from Bottleneck) (1.17.4)
Building wheels for collected packages: Bottleneck
  Building wheel for Bottleneck (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: /home/filholf/pycamlar/pycamlar/bin/python /home/filholf/pycamlar/pycamlar/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmpzdoiga7s
       cwd: /tmp/pip-install-gx8dza5k/Bottleneck
  Complete output (122 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.7
  creating build/lib.linux-x86_64-3.7/bottleneck
  copying bottleneck/__init__.py -> build/lib.linux-x86_64-3.7/bottleneck
  copying bottleneck/_pytesttester.py -> build/lib.linux-x86_64-3.7/bottleneck
  copying bottleneck/_version.py -> build/lib.linux-x86_64-3.7/bottleneck
  creating build/lib.linux-x86_64-3.7/bottleneck/benchmark
  copying bottleneck/benchmark/__init__.py -> build/lib.linux-x86_64-3.7/bottleneck/benchmark
  copying bottleneck/benchmark/autotimeit.py -> build/lib.linux-x86_64-3.7/bottleneck/benchmark
  copying bottleneck/benchmark/bench.py -> build/lib.linux-x86_64-3.7/bottleneck/benchmark
  copying bottleneck/benchmark/bench_detailed.py -> build/lib.linux-x86_64-3.7/bottleneck/benchmark
  creating build/lib.linux-x86_64-3.7/bottleneck/slow
  copying bottleneck/slow/__init__.py -> build/lib.linux-x86_64-3.7/bottleneck/slow
  copying bottleneck/slow/move.py -> build/lib.linux-x86_64-3.7/bottleneck/slow
  copying bottleneck/slow/nonreduce.py -> build/lib.linux-x86_64-3.7/bottleneck/slow
  copying bottleneck/slow/nonreduce_axis.py -> build/lib.linux-x86_64-3.7/bottleneck/slow
  copying bottleneck/slow/reduce.py -> build/lib.linux-x86_64-3.7/bottleneck/slow
  creating build/lib.linux-x86_64-3.7/bottleneck/src
  copying bottleneck/src/__init__.py -> build/lib.linux-x86_64-3.7/bottleneck/src
  copying bottleneck/src/bn_config.py -> build/lib.linux-x86_64-3.7/bottleneck/src
  copying bottleneck/src/bn_template.py -> build/lib.linux-x86_64-3.7/bottleneck/src
  creating build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/__init__.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/input_modification_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/list_input_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/memory_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/move_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/nonreduce_axis_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/nonreduce_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/reduce_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/scalar_input_test.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  copying bottleneck/tests/util.py -> build/lib.linux-x86_64-3.7/bottleneck/tests
  UPDATING build/lib.linux-x86_64-3.7/bottleneck/_version.py
  set build/lib.linux-x86_64-3.7/bottleneck/_version.py to '1.3.1'
  running build_ext
  running config
  compiling '_configtest.c':

  #pragma GCC diagnostic error "-Wattributes"

  int __attribute__((optimize("O3"))) have_attribute_optimize_opt_3(void*);

  int main(void)
  {
      return 0;
  }

  gcc -pthread -B /home/filholf/miniconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -c _configtest.c -o _configtest.o
  failure.
  removing: _configtest.c _configtest.o
  compiling '_configtest.c':

  #ifndef __cplusplus
  static inline int static_func (void)
  {
      return 0;
  }
  inline int nostatic_func (void)
  {
      return 0;
  }
  #endif
  int main(void) {
      int r1 = static_func();
      int r2 = nostatic_func();
      return r1 + r2;
  }

  gcc -pthread -B /home/filholf/miniconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -c _configtest.c -o _configtest.o
  failure.
  removing: _configtest.c _configtest.o
  compiling '_configtest.c':

  #ifndef __cplusplus
  static __inline__ int static_func (void)
  {
      return 0;
  }
  __inline__ int nostatic_func (void)
  {
      return 0;
  }
  #endif
  int main(void) {
      int r1 = static_func();
      int r2 = nostatic_func();
      return r1 + r2;
  }

  gcc -pthread -B /home/filholf/miniconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -c _configtest.c -o _configtest.o
  failure.
  removing: _configtest.c _configtest.o
  compiling '_configtest.c':

  #ifndef __cplusplus
  static __inline int static_func (void)
  {
      return 0;
  }
  __inline int nostatic_func (void)
  {
      return 0;
  }
  #endif
  int main(void) {
      int r1 = static_func();
      int r2 = nostatic_func();
      return r1 + r2;
  }

  gcc -pthread -B /home/filholf/miniconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -c _configtest.c -o _configtest.o
  failure.
  removing: _configtest.c _configtest.o
  building 'bottleneck.reduce' extension
  creating build/temp.linux-x86_64-3.7
  creating build/temp.linux-x86_64-3.7/bottleneck
  creating build/temp.linux-x86_64-3.7/bottleneck/src
  gcc -pthread -B /home/filholf/miniconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-build-env-i9jvt975/overlay/lib/python3.7/site-packages/numpy/core/include -I/home/filholf/miniconda3/include/python3.7m -Ibottleneck/src -c bottleneck/src/reduce.c -o build/temp.linux-x86_64-3.7/bottleneck/src/reduce.o -O2
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for Bottleneck
  Running setup.py clean for Bottleneck
Failed to build Bottleneck
ERROR: Could not build wheels for Bottleneck which use PEP 517 and cannot be installed directly

The text was updated successfully, but these errors were encountered:

lcflorindo · 2019-11-29T14:48:14Z

QUICK UPDATE I took some time to research the internet about: PEP517 have some problems with virtualenvs but i already tried --no-use-pep517 with no success and still retrying an error.

qwhelan · 2019-11-29T22:29:38Z

Could you provide the pip version?

Thanks for reporting!

qwhelan · 2019-11-30T23:45:09Z

On further investigation, I found this pypa/pip#6256 which suggests the issue is that wheels simply aren't supported with PEP 517 builds. My best guess would be to pip install --upgrade pip setuptools wheel and that should resolve the issue.

lcflorindo · 2019-12-02T17:30:07Z

Could you provide the pip version?

Thanks for reporting!

pip 19.2.3 from /home/filholf/anaconda3/lib/python3.7/site-packages/pip (python 3.7)

I'm assuming that my OS is not helping as well, I'm using Suse 12 SP4, my other server is an Ubuntu 16.04lts and everything worked fine...

lcflorindo · 2019-12-02T17:45:06Z

On further investigation, I found this pypa/pip#6256 which suggests the issue is that wheels simply aren't supported with PEP 517 builds. My best guess would be to pip install --upgrade pip setuptools wheel and that should resolve the issue.

I tried the upgrade, but stills returning the wheel problem. I'm totally able to install it at base.

But as a quick update, I solved installing Anaconda instead of miniconda, but not sure about the relation of both or even what was the problem with miniconda. Could it be a repair when I uninstalled/installed.

qwhelan · 2019-12-03T03:53:53Z

Hmm, there really shouldn't be a difference between equivalent versions of Miniconda/Anaconda.

Good to hear it's resolved and apologies for not having a clear answer here. Please feel free to re-open if it re-surfaces.

AnakTeka · 2020-01-02T11:18:32Z

I'm receiving a same error and using python:3.6-slim docker image, I fixed it by installing gcc inside the container.

harshikanu · 2020-01-03T20:02:44Z

Another way to resolve this is to download Windows SDK 10 (latest version). If this alone doesn't work then download Visual Studio 2019 (again whichever is the latest version). This updates the wheel process.

bchen32 · 2020-02-21T00:57:02Z

harshikanu's suggestion worked for me. I'd like to expand on it a little bit

Go to visual studio downloads at https://visualstudio.microsoft.com/downloads/
Scroll down to 'All Downloads'
Click the dropdown for 'Tools for Visual Studio 2019'
Download 'Build Tools for Visual Studio 2019'

and that should successfully update wheel and allow you to install bottleneck

qwhelan · 2020-02-21T03:53:26Z

@StormFalcon32 Do you happen to know the version of the Windows SDK you were on pre-upgrade? And pip and python as well?

bchen32 · 2020-02-21T04:02:15Z

Oh man I don't remember what version of Windows sdk but I was on Python 3.7.6 and I think 20.0.2 on pip

qwhelan · 2020-02-21T06:50:40Z

Thanks for checking - was mostly wondering if this was connected to the Python 3.8 issue some Arch users had reported (and should be fixed by 1.3.2 that I released a few minutes ago)

bayesfactor · 2020-02-26T07:53:14Z

I installed Build Tools for Visual Studio 2019, updated wheels, and I still have the error when installing Bottleneck-1.3.2.:
Failed to build bottleneck
ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly

python 3.5.5
wheel 0.34.2
pip 20.0.2

harshikanu · 2020-02-26T22:15:01Z

@bayesfactor I think you need to have the latest version of python installed.

rhandberg · 2020-03-16T19:12:33Z

I am getting the same error with Bottleneck 1.3.2 on a Linux machine with Python 3.6.3, and the newest versions of pip and setuptools... It works fine with 1.3.1... Any ideas?

corysm1th · 2020-03-17T15:01:27Z

@rhandberg I had the same issue on CentOS. My output contained the following error:
bottleneck/src/bottleneck.h:6:20: fatal error: Python.h: No such file or directory #include <Python.h> ^
Which I solved by installing the python3 source
yum install -y python3-devel

codrutartene · 2020-03-20T13:22:28Z

I'm receiving a same error and using python:3.6-slim docker image, I fixed it by installing gcc inside the container.

same error using ubuntu:18.04 with minconda and python==3.7; fixed by installing build-essential.

muneale · 2020-04-03T08:16:11Z

I got the same issue when I execute:
$ pipenv install bottleneck

I solved the problem with:
$ python3.7 -m pipenv install bottleneck

OS: Ubuntu 18.04 LTS
Python: 3.7
Pip: 20.0.2
Bottleneck: 1.3.2

rasihilp · 2020-05-08T08:03:32Z

If still having issue, can try below steps. It worked for windows
https://medium.com/@pierre_guillou/how-to-install-fastai-v1-on-windows-10-ca1bc370dce4

talha1503 · 2020-05-12T18:50:10Z

I'm having the same issue.
OS: Windows 10
Python : 3.8
pip:19.2.3
Bottleneck:1.3.2

I have also installed Build Tools for Visual Studio 2019.

neelnova · 2020-05-26T13:29:20Z

harshikanu's suggestion worked for me. I'd like to expand on it a little bit

Go to visual studio downloads at https://visualstudio.microsoft.com/downloads/

Scroll down to 'All Downloads'

Click the dropdown for 'Tools for Visual Studio 2019'

Download 'Build Tools for Visual Studio 2019'

and that should successfully update wheel and allow you to install bottleneck

I am using python version - 3.6.0
still, I am getting error like

Failed building wheel for bottleneck
Running setup.py clean for bottleneck
Failed to build bottleneck
Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly

SergeiMerson-StartUpAI · 2020-05-27T19:14:48Z

Hi,
I solved this issue by downloading appropriate version of line_profiler from:
https://www.lfd.uci.edu/~gohlke/pythonlibs/#line_profiler
and then installing it using "pip install your_package_version_.whl"
Hope that it would help

marcmaxson · 2020-05-29T03:43:44Z

I couldn't get pipenv update to work with hdbscan but pip install -r requirements.txt worked for me on MacOS and in the docker container I was putting this into for AWS.

kevinsingapore · 2020-06-02T03:20:43Z

i got the same error;
os: centos7-aarch64
python verison: 3.6.8
pip version: 20.1.1
and the error info：

ERROR: Could not build wheels for numpy which use PEP 517 and cannot be installed directly

and how to solve the error？

nanounanue · 2020-06-02T16:09:27Z

Same error in alpine:latest image with python 3.8 and pip-19.2.3

ee07dazn · 2020-06-03T10:34:30Z

Downgrading the pip version sorted the issue for me : pip install pip==18.1

fengmang-k · 2020-10-31T06:40:52Z

for windows I installed c++ complier solved this problem

firefresh · 2020-11-09T22:45:56Z

For alpine linux i fixed with:
apk add gcc libc-dev

check it with apt or etc in your linux distribution

ag-hcoder · 2020-11-18T07:05:07Z

Use sudo

nastynaz · 2020-12-02T22:23:20Z

For alpine I needed apk add gcc libc-dev g++

Neele22 · 2021-01-12T10:24:07Z

I have the same issue when running
pipenv install django-oscar

Error message: Could not build wheels for oscar which use PEP 517 and cannot be installed directly

I am using Windows 10 Home 1909, Python 3.8, pipenv 2018.11.26, and VScode 1.52.1

reyesGeorge · 2021-01-18T21:47:36Z

I was having the same problem for Mac: ERROR: Failed building wheel for pycairo
While installing cairo into a virtual env. I solved by running:

first: brew install cairo pkg-config
then: pip install cairo

one-two-one-two · 2021-03-15T16:04:35Z

#281 (comment)

Same here, in a dockerfile from python:3.7-slim-buster
adding
RUN apt-get update && apt-get install -y build-essential
solves the issue

Edit: On a linux server (as opposed to the docker image above) i also had to install python3.6-dev

jl710107 · 2021-03-27T01:17:58Z

Hoy vienes 26 de marzo del 2021
Reporto este error al instalar pynacl
En mi móvil A01 CORE DE SAMSUNG EN LA APP TERMUX
Si es posible darme alguna solución lo agradesere.
ERROR: Failed building wheel for pynacl
Failed to build pynacl
ERROR: Could not build wheels for pynacl which use PEP 517 and cannot be installed directly.
Gracias

gmt710 · 2021-04-13T02:46:41Z

https://stackoverflow.com/questions/64038673/could-not-build-wheels-for-which-use-pep-517-and-cannot-be-installed-directly

It may helps.

gmt710 · 2021-04-13T02:47:56Z

https://stackoverflow.com/questions/64038673/could-not-build-wheels-for-which-use-pep-517-and-cannot-be-installed-directly

It may helps.

jokerarthur28 · 2021-04-14T07:05:17Z

I'm receiving a same error and using python:3.6-slim docker image, I fixed it by installing gcc inside the container.

how to install gcc inside the container?

mortada · 2021-05-31T06:01:51Z

I ran into this same error and resolved it by doing either one of the following two ways:

run the install command with an extra argument: pip install --no-use-pep517
downgrade pip from 21.x to 20.3 , then the simple pip install works for me again (see the context here: Deprecate call to setup.py install when building a wheel failed for source distributions without pyproject.toml pypa/pip#8368)

pavankumarg1729 · 2021-06-28T08:56:34Z

for windows I installed c++ complier solved this problem

this worked for me too

DataPhill · 2021-08-09T19:46:05Z

Hi All, having troubles installing fancyImpute ???

Open the atched file :
[requirements.txt]

(https://github.com/pydata/bottleneck/files/6956991/requirements.txt)

Install each dependency in the txt file separately:

Since, i have noticed the cvxpy gives the error when installing:

ERROR: Failed building wheel for scs
Failed to build scs
ERROR: Could not build wheels for scs which use PEP 517 and cannot be installed directly

Then: use the following command to install it:

conda install -c conda-forge cvxpy

finally then 👍

pip install fancyimpute

#281

vlnahp · 2021-09-08T06:27:11Z

I had the same problem with coincurve, and the solution was unbelievably easy!

I simply installed the lowest version that meets my needs. And it worked!

The latest version was 15.0.1 and I installed version 4.4.0 without any error.

SSI7210153 · 2021-09-30T23:15:37Z

harshikanu's suggestion worked for me. I'd like to expand on it a little bit

Go to visual studio downloads at https://visualstudio.microsoft.com/downloads/

Scroll down to 'All Downloads'

Click the dropdown for 'Tools for Visual Studio 2019'

Download 'Build Tools for Visual Studio 2019'

and that should successfully update wheel and allow you to install bottleneck

This solution worked. Thank you. I took advantage of and installed some packages for my visual studio code and also some tools to compile Cmakes.

lcflorindo closed this as completed Dec 2, 2019

qwhelan mentioned this issue Mar 23, 2020

Make installation process more robust for users #337

Merged

denphi mentioned this issue Apr 21, 2020

Error installing floatview in Docker denphi/jupyterlab-floatview#5

Closed

1ycx mentioned this issue May 5, 2020

ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly #344

Open

jkterry1 mentioned this issue Oct 2, 2020

Visual studio problem Farama-Foundation/PettingZoo#216

Closed

carloelle mentioned this issue Oct 23, 2020

pip install issue version 0.8.2. (PEP 517 error) vtraag/leidenalg#49

Closed

riverrun mentioned this issue Nov 18, 2020

Unable to install riverrun/genxword#24

Open

gennaro-tedesco mentioned this issue Dec 22, 2020

Pipenv failed to build wheels (PEP 517) pypa/pipenv#4576

Closed

M00NSH0T mentioned this issue Jan 15, 2021

Does not work with Jupyter Lab 3 jupyterlab-contrib/jupyterlab-variableInspector#172

Closed

lckr mentioned this issue Jan 20, 2021

Cannot install on Jupyter Lab 3.0.5 jupyterlab-contrib/jupyterlab-variableInspector#183

Closed

MaartenGr mentioned this issue Feb 20, 2021

Error when install on windows MaartenGr/BERTopic#62

Closed

erogol mentioned this issue Apr 11, 2021

[Bug] Not able to install coqui-ai/TTS#421

Closed

jorgehumberto mentioned this issue Jun 1, 2021

installation error njcuk9999/lbl#10

Closed

seekyou123 mentioned this issue Jun 17, 2021

Failing in installing celescope singleron-RD/CeleScope#28

Closed

gurusura mentioned this issue Jun 29, 2021

Failed to build scs ERROR: Could not build wheels for scs which use PEP 517 and cannot be installed directly ssantoshp/Empyrial#25

Closed

wkuopt mentioned this issue Oct 2, 2021

[BUG]building docker image fails pycaret/pycaret#1575

Closed

ivadym mentioned this issue Oct 12, 2021

Balsamic container installation fails unexpectedly Clinical-Genomics/BALSAMIC#791

Closed

Lkruitwagen mentioned this issue Jan 28, 2022

rm xskillscore dependency H2Oxford/h2ox-ai#1

Closed

'ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly' #281

'ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly' #281

Comments

lcflorindo commented Nov 29, 2019

lcflorindo commented Nov 29, 2019

qwhelan commented Nov 29, 2019

qwhelan commented Nov 30, 2019

lcflorindo commented Dec 2, 2019 • edited

lcflorindo commented Dec 2, 2019 • edited

qwhelan commented Dec 3, 2019

AnakTeka commented Jan 2, 2020

harshikanu commented Jan 3, 2020

bchen32 commented Feb 21, 2020

qwhelan commented Feb 21, 2020

bchen32 commented Feb 21, 2020

qwhelan commented Feb 21, 2020

bayesfactor commented Feb 26, 2020

harshikanu commented Feb 26, 2020

rhandberg commented Mar 16, 2020

corysm1th commented Mar 17, 2020 • edited

codrutartene commented Mar 20, 2020

muneale commented Apr 3, 2020

rasihilp commented May 8, 2020

talha1503 commented May 12, 2020

neelnova commented May 26, 2020 • edited

SergeiMerson-StartUpAI commented May 27, 2020

marcmaxson commented May 29, 2020

kevinsingapore commented Jun 2, 2020

nanounanue commented Jun 2, 2020 • edited

ee07dazn commented Jun 3, 2020

fengmang-k commented Oct 31, 2020

firefresh commented Nov 9, 2020

ag-hcoder commented Nov 18, 2020

nastynaz commented Dec 2, 2020

Neele22 commented Jan 12, 2021

reyesGeorge commented Jan 18, 2021

one-two-one-two commented Mar 15, 2021 • edited

jl710107 commented Mar 27, 2021

gmt710 commented Apr 13, 2021

gmt710 commented Apr 13, 2021

jokerarthur28 commented Apr 14, 2021

mortada commented May 31, 2021

pavankumarg1729 commented Jun 28, 2021

DataPhill commented Aug 9, 2021 • edited

vlnahp commented Sep 8, 2021

SSI7210153 commented Sep 30, 2021

lcflorindo commented Dec 2, 2019 •

edited

lcflorindo commented Dec 2, 2019 •

edited

corysm1th commented Mar 17, 2020 •

edited

neelnova commented May 26, 2020 •

edited

nanounanue commented Jun 2, 2020 •

edited

one-two-one-two commented Mar 15, 2021 •

edited

DataPhill commented Aug 9, 2021 •

edited