When I created a virtual environment after a long time and tried to install pyinstaller with the pip command, an error occurred. Probably the same cause as the error that occurred in pyautogui in the past. ↑ [Python] pyautogui (PyMsgBox) Provisional measures against installation errors ** I solved it after installing "wheel" **, so make a note.
When installing pyinstaller with pip, the installation fails with the following error content.
(pyautogui_pillow) PS C:\Users\aaa\Desktop\python\10_Right click tool> pip install pyinstaller Collecting pyinstaller Using cached pyinstaller-4.1.tar.gz (3.5 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing wheel metadata ... error ERROR: Command errored out with exit status 1: : creating 'C:\Users\aaa\AppData\Local\Temp\pip-modern-metadata-f8yl8_co\pyinstaller.dist-info' error: invalid command 'bdist_wheel' ---------------------------------------- ERROR: Command errored out with exit status 1: 'c:\users\aaa\desktop\python\pyautogui_pillow\scripts\python.exe' 'c:\users\aaa\desktop\python\pyautogui_pillow\lib\site-packages\pip\_vendor\pep517\_in_process.py' prepare_metadata_for_build_wheel 'C:\Users\aaa\AppData\Local\Temp\tmpo72l8jp6' Check the logs for full command output.
It is written that the wheel deployment failed in the third line from the bottom, so this area is suspicious.
Just install wheel with pip.
> pip install wheel
After that, you can reinstall the library with the error again with pip. For the time being, "py installer" and "py autogui" that had an error could be installed by this method.
wheel is one of the python packaging formats. It seems that eggs used to be the mainstream packaging format, but nowadays wheels are mostly used. In this case, it is expected that the packaging format of the latest version of the library has changed and it is no longer possible to deploy the wheel in the existing environment. (I haven't updated the python environment, so there may be a root cause in that.)
By the way, it seems that many pip errors are caused by proxies or PC administrator privileges. If you are using it in an in-house LAN environment, please doubt that as well.