'ERROR: Could not build wheels for bottleneck which use PEP 517 and cannot be installed directly'
See original GitHub issueHi, 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
Issue Analytics
- State:
- Created 4 years ago
- Reactions:31
- Comments:56
Top Results From Across the Web
ERROR: Could not build wheels for scipy which use PEP 517 ...
The error message was almost the same: ERROR: Could not build wheels for xmlsec which use PEP 517 and cannot be installed directly....
Read more >ERROR: Could not build wheels for bottleneck which use PEP ...
I just ran "sudo apt-get install python-dev" inside the venv. It installed successfully, but I get the same error when I try to...
Read more >ERROR: Could not build wheels for mujoco-py which use PEP ...
Failed to build mpi4py ERROR: Could not build wheels for mpi4py which use PEP 517 and cannot be installed directly 我们按照(参考1:https://blog.
Read more >error: could not build wheels for pyaudio which use pep 517 ...
Sometimes this can be due to a cache issue and the no-binary flag won't work. In which case try pip install <insert package...
Read more >pip: Could not build wheels for which use PEP 517 and cannot ...
문제: Could not build wheels for (이름) which use PEP 517 and cannot be installed directly 위 메시지와 함께 pip install이 실패함 해결:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

On further investigation, I found this https://github.com/pypa/pip/issues/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 wheeland that should resolve the issue.harshikanu’s suggestion worked for me. I’d like to expand on it a little bit
and that should successfully update wheel and allow you to install bottleneck