ERROR: Failed building wheel for aiohttp #8181
-
Windows 11. Currently Running: Python 3.12.2 I have been trying to install module Every time I try and install the above module, I run into the error mentioned below. I have tried to fix this issue by installing some other aiohttp versions viz. 'aiohttp v 3.9.4.rc0, 3.9.3, 3.9.2, 3.9.1, 3.9.0 but every time I have been stonewalled by the said error. Downgrading my Python version to 3.11.0 as suggested by a few users on various forums is a very difficult option for me due to many other installed modules starting to show issues. Is there any likelihood of an updated version of module 'aiohttp' addressing the mentioned issue coming out shortly? Appreciate any suggestion on any other workaround to mitigate this issue. `Building wheels for collected packages: aiohttp × Building wheel for aiohttp (pyproject.toml) did not run successfully. note: This error originates from a subprocess, and is likely not a problem with pip. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
The latest versions of aiohttp come with pre-built wheels that pip picks automatically, by default. If it doesn't for you for some reason, that would indicate that you changed/overrode the configuration of pip somewhere to build from source. It's not something that we can help with as only you know what you did. If you let pip install from wheels (with something like P.S. The log snippet you posted is from the older aiohttp versions. It's impossible that it's exactly the same for the recent ones. |
Beta Was this translation helpful? Give feedback.
-
Thanks webknjaz for your advice. However, I have never touched the pip configuration. The only thing I do once in a while is to update pip using the command Now what do you think I should do to get out of this fix, even if it means uninstalling the entire pip package. |
Beta Was this translation helpful? Give feedback.
The latest versions of aiohttp come with pre-built wheels that pip picks automatically, by default. If it doesn't for you for some reason, that would indicate that you changed/overrode the configuration of pip somewhere to build from source. It's not something that we can help with as only you know what you did. If you let pip install from wheels (with something like
--prefer-binary
or--only-binary
), it won't be attempting to build from sdist.P.S. The log snippet you posted is from the older aiohttp versions. It's impossible that it's exactly the same for the recent ones.