Skip to content

Commit 8dbb8b9

Browse files
authored
Don't check for wheel when only build-system.requires is present (#11674)
1 parent c4566c6 commit 8dbb8b9

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

news/11673.bugfix.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Stop checking that ``wheel`` is present when ``build-system.requires``
2+
is provided without ``build-system.build-backend`` as ``setuptools``
3+
(which we still check for) will inject it anyway.

src/pip/_internal/pyproject.py

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -159,9 +159,8 @@ def load_pyproject_toml(
159159
if backend is None:
160160
# If the user didn't specify a backend, we assume they want to use
161161
# the setuptools backend. But we can't be sure they have included
162-
# a version of setuptools which supplies the backend, or wheel
163-
# (which is needed by the backend) in their requirements. So we
164-
# make a note to check that those requirements are present once
162+
# a version of setuptools which supplies the backend. So we
163+
# make a note to check that this requirement is present once
165164
# we have set up the environment.
166165
# This is quite a lot of work to check for a very specific case. But
167166
# the problem is, that case is potentially quite common - projects that
@@ -170,6 +169,6 @@ def load_pyproject_toml(
170169
# tools themselves. The original PEP 518 code had a similar check (but
171170
# implemented in a different way).
172171
backend = "setuptools.build_meta:__legacy__"
173-
check = ["setuptools>=40.8.0", "wheel"]
172+
check = ["setuptools>=40.8.0"]
174173

175174
return BuildSystemDetails(requires, backend, check, backend_path)

0 commit comments

Comments
 (0)