You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setuptools declares wheel as a wheel build dependency for PEP 517 builds already via a build hook. Both pip 24 (pypa/pip#12449) and build 1.1 (pypa/build#716) have removed wheel from the default PEP 517 fallback environment. I think uv should do the same.
There are a small collection of packages that import wheel inside setup.py directly, which is discouraged by wheel (as there's no official pubic API), and these packages should either declare wheel explicitly as a dependency in pyproject.toml, protect the import, or use setuptool's functionality to get a build class without importing it.
The text was updated successfully, but these errors were encountered:
They also won't work with pip or build. :) The most recent issue was one with pyodide pyodide/pyodide#4593 - the user forgot to copy the pyproject.toml into the docker container when building. :) Another: pypa/build#750. I think pip took the brunt of this, though, as pip 24 came out before build 1.1, and people using build tend to be more likely to have pyproject.tomls, etc., so looking around in pip's issue tracker might be helpful.
Setuptools declares wheel as a wheel build dependency for PEP 517 builds already via a build hook. Both pip 24 (pypa/pip#12449) and build 1.1 (pypa/build#716) have removed wheel from the default PEP 517 fallback environment. I think uv should do the same.
There are a small collection of packages that
import wheel
inside setup.py directly, which is discouraged bywheel
(as there's no official pubic API), and these packages should either declare wheel explicitly as a dependency in pyproject.toml, protect the import, or use setuptool's functionality to get a build class without importing it.The text was updated successfully, but these errors were encountered: