Could not build wheels for XXX which use PEP 517
See original GitHub issue- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- OS version and name: macOS 10.15
- Poetry version: 1.0.0b4
Issue
#11 provides a workaround for custom build systems (e.g., Cython extensions) that works well with poetry. However, when you try to do pip install .
on a project that has a custom build.py
the build process fails with
ERROR: Could not build wheels for seiya which use PEP 517 and cannot be installed directly
This means, among other things, that one cannot use ReadTheDocs to document the code. This happens with my code but I have also tested it with pendulum.
Is there a workaround for this?
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
Could not build wheels for numpy which use PEP 517 and ...
I got this below error message. Failed to build numpy ERROR: Could not build wheels for numpy which use PEP 517 and cannot...
Read more >Could not build wheels for PyGObject which use PEP 517 and ...
Could not build wheels for PyGObject which use PEP 517 and cannot be installed directly. #358 (closed) (This solution doesn't solve problem either)....
Read more >pyproject.toml with no build-system.requires - Distutils-SIG
When the build-system.requires key is missing, pip falls back to assuming it should be ["setuptools", "wheel"]. The in-development version of pip currently ...
Read more >pip install - pip documentation v21.1.dev0
This section is only about installation order of runtime dependencies, and does not apply to build dependencies (those are specified using PEP 518)....
Read more >Could not build wheels for hdbscan which use PEP 517 and ...
Problem尝试用pip 在命令行安装hdbscan 时,发生如下报错pip install hdbscan...Building wheels for collected packages: hdbscan Building wheel ...
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 FreeTop 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
Top GitHub Comments
Doing some more Googling on this I came up with the solution described here. One can create a
setup.py
file such asand remove the need of using
build.py
. As far as I can see this works fine (even allows editable installs!). When you dopoetry install
it creates anUNKNOWN.egg-info
directory withPKG-INFO
in which all the fields areUNKNOWN
. That does not seem to affect poetry but I’m not sure what will happen when you build a distribution (I have runpoetry build
and the results look ok, with the correct metadata, but I haven’t tested it all the way by uploading it to PyPI and installing from a fresh environment).IMHO poetry really needs to define a way to deal with extensions. There are many projects that depend on a custom build system and this kind of workarounds are getting old …
I use python 3.8.0, and this problem still occurs