v0.46.0 Breaking CI build pipelines

[fervand1]

Summary

The latest release v0.46.0 is breaking the pipelines which were previously working. The following error is raised.

      [stderr]
      error: invalid command 'bdist_wheel'

      hint: This error likely indicates that `mypackage @ file:///D:/test/myrepo/mypackage`
      depends on `wheel`, but doesn't declare it as a build dependency. If `mypackage @
      file:///D:/test/myrepo/mypackage` is a first-party package, consider adding `wheel` to
      its `build-system.requires`. Otherwise, `uv pip install wheel` into the environment and re-run with
      `--no-build-isolation`.

Although wheel is not the direct dependency, I have following configuration, where wheel is dependency of mybuildtools package.

[build-system]
requires = ["setuptools", "mybuildtools"]
build-backend = "setuptools.build_meta"

What has changed in the new release that is causing the issue and why it needs to be explicit dependency and not sub dependency? I think the previous version was doing it correctly.

Note: If I downgrade to v0.45.0, the pipelines are succeeding correctly

Platform

Windows 11

Version

v0.46.0

Python version

3.10

[agronholm]

Duplicate, and already resolved by yanking the release.

[agronholm]

Hm, I am now wondering if this is truly a duplicate.

[agronholm]

I see that your build requirements don't specify a minimum version, so it could be using a old setuptools version from cache that doesn't vendor bdist_wheel. Updating it to specify setuptools >= 70.1 should resolve any problems going forward.

[agronholm]

Is mybuildtools your own thing? What does its pyproject.toml looks like? Remember that wheel doesn't have a public API, so importing it is a bad idea.

[fervand1]

@agronholm Hi yes it is a inhouse build library

pyproject.toml just looks like that

[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.black]
line-length = 120
skip-string-normalization = true

[tool.isort]
multi_line_output = 3

[tool.flake8]
max-line-length = 132

[tool.pycodestyle]
max-line-length = 132

But we are still maintaining compatibility with python 2 for some of our work so we also have setup.cfg which lists other dependencies see below. I see setuptools was listed to be > 65.

[metadata]
name = mybuildtools
version = 3.0.0

[options]
package_dir =
     = src
packages = find:
zip_safe = False
install_requires =
    setuptools; python_version=='2.7'
    setuptools>65; python_version >= '3.9'
    wheel
    jinja2
    jsonschema
    pathlib; python_version=='2.7'
    pytest<5; python_version == '2.7'
    pytest; python_version >= '3.9'
    six
    uv; python_version >= '3.9'
include_package_data = True

[fervand1]

@agronholm is it possible to get the whl file of the yanked version 0.46.0 ? I could test it by trying your suggestion of listing setuptools>=70.1 . I can no longer install it with pip command

[agronholm]

@agronholm is it possible to get the whl file of the yanked version 0.46.0 ? I could test it by trying your suggestion of listing setuptools>=70.1 . I can no longer install it with pip command

You can just depend on wheel==0.46.0.

[agronholm]

@agronholm is it possible to get the whl file of the yanked version 0.46.0 ? I could test it by trying your suggestion of listing setuptools>=70.1 . I can no longer install it with pip command

You can just depend on wheel==0.46.0.

Due to this, that won't work either.

[fervand1]

@agronholm FYI, I did the following steps

1. pip install wheel==0.46.0
2. In setup.cfg, setuptools>=70.1; python_version >= '3.9'
3. Installed mybuildtools, which pulled latest setuptools v78
4. Ran installation commands, and it worked

To reproduce again,

1. uninstalled setuptools
2. Installed older version of setuptools I had on the system 65.5.0
3. Reset setup.cfg, setuptools>65; python_version >= '3.9'
4. Installed mybuildtools, it didn't pull new version this time as requirement was satisfied
5. Ran installation commands, and it reproduced.

So suggestion of setting setuptools>=70.1 works

[agronholm]

I'm confused. Can you clarify which version of setuptools was actually installed? There's a range of versions which would actually work, but the latest release shouldn't.

[fervand1]

setuptools version 78.1.0

[fervand1]

@agronholm Double checked. Upgraded just the setuptools in the venv. It took 78.1.0. Error was gone

[agronholm]

OK, but that also means it will not use wheel v0.46.0 because it's yanked, right?