Reputation: 1961

Could not build wheels for _ which use PEP 517 and cannot be installed directly

I am trying to install a package which uses PEP 517. The newest version of Pip won't allow me to install it due to an error involving building wheels for PEP 517.

In the past, I've solved this issue by downgrading Pip, installing the package and upgrading Pip back to the latest version. However, after I downgrade pip in my virtualenv, if I try to run pip install black I get the error

No module named 'pip._internal.cli.main'

How can I solve this?

Upvotes: 67

Answers (13)

Max Mougg

Reputation: 29

I had the error trying to install with poetry so I used:

pip install _____ --no-cache-dir

(where _____ is whatever package you are looking for) directly from the venv shell and it worked.

Upvotes: 1

prikarsartam

Reputation: 21

Simplest solution that works for me each time -

pip install <package_name> --use-pep517

Upvotes: 2

Delyan Raychev

Reputation: 21

You can try this -->

pip install --use-pep517 'package_name'

Upvotes: 2

Michael Oberst

Reputation: 101

No posted solutions worked for me (trying to install packages via poetry in my case).

Fixed it for myself, and it turns out it was a rouge conda installation - I discovered (when looking at the failed builds) that it was using *.h files from my miniconda installation, which was weird to me, since I would have expected that to be isolated from poetry (which I installed via pipx).

Solution in my case was to wipe out conda entirely (I don't really need it), and then poetry install ... worked like a charm.

Upvotes: 0

Zaraki Kenpachi

Reputation: 5740

Check if you have python dev part installed. If not then:

sudo apt update
sudo apt install python3.X-dev

Upvotes: 3

Joel Oduro-Afriyie

Reputation: 2053

This solution from this link helped me:

pip install --upgrade pip setuptools wheel

Upvotes: 21

Christopher Broderick

Reputation: 448

On OSX setting SYSTEM_VERSION_COMPAT=1 in my environment prior to running pip solved it:

export SYSTEM_VERSION_COMPAT=1

Upvotes: 1

yubari

Reputation: 1

I have also encountered the same issue when uninstalling and reinstalling miniconda.

I have no idea why, but in my registry key Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor AutoRun has been set to if exist. I deleted the value then it worked fine just as before.

Upvotes: -7

o0lemon_pie0o

Reputation: 71

When I ran into this error, the problem was that the package I was pulling had its metadata configured incorrectly, which caused building the wheels to fail.

To find that error I ran, pip --verbose install <my_package> Which let me see what about the wheel build was failing, and fix it upstream.

Upvotes: 7

KevinG

Reputation: 139

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 names> --no-cache-dir.

This seems to be a frequent issue when installing packages with python. First, check to ensure you have activated the virtualenv you think you're supposed to be in, then check to see if you have wheels pkg (pip install wheel if not). If those fail then the --no-cache-dir or --no-binary flags come into play. Reading the pypi documentation on each package could help as well. Best of luck!

Upvotes: 9

Alexander Santos

Reputation: 1701

Posting an answer as reference for future searchers here.

I tried installing Pillow and got this error. Tried many different approaches, none of them worked. Then i downgraded Python (From 3.9) to 3.8 and just tried installing by pip again, then it worked.

If it fails for you, try downgrading Python, and it may work.

Upvotes: 5

Mleen

Reputation: 374

This error came up for the h5py library during the installation of Tensorflow. I checked the h5py documentation to make sure I had the right versions of pip and setuptools, https://pip.pypa.io/en/stable/reference/pip/.

pip install --upgrade pip setuptools wheel

I then checked the error log to identify what has caused h5py to fail while installing backend dependencies. I identified it was the libhdf5.so, where it says "error: libhdf5.so cannot open shared object file: No such file or directory". I installed the library by running:

sudo apt-get install libhdf5-dev

After this, the h5py installed successfully alongside TensorFlow. I've come across similar PEP 517 errors caused by missing dependencies:

Upvotes: 27

Sean Payne

Reputation: 1961

The easiest solution to deal with the error

"Could not build wheels for ____ which use PEP 517 and cannot be installed directly"

is the following:

sudo pip3 install _____ --no-binary :all:

Where ____ is obviously the name of the library you want to install.

Upvotes: 26

Could not build wheels for _ which use PEP 517 and cannot be installed directly

Answers (13)

Related Questions