wheels accumulate libs from different versions

[nschloe]

I'm using cibuildwheels on gh-actions to compile my Python code into wheels. This is my config:

      - name: Build wheels
        uses: pypa/cibuildwheel@v2.3.1
        env:
          CIBW_BUILD: cp37-* cp38-* cp39-* cp310-*
          CIBW_SKIP: "*-musllinux*"
          CIBW_ARCHS: native

This produces the output files

foobar-1.0.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
foobar-1.0.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
foobar-1.0.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
foobar-1.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

I noticed that

• the cp37-wheel contains the cp37 lib,
• the cp38-wheel contains the cp38 lib and the cp37 lib,
• the cp39-wheel contains the cp39 lib and the cp38 lib and the cp37 lib,
• the cp310-wheel contains the cp310 lib and cp39 lib and the cp38 lib and the cp37 lib.

Any idea what's going wrong here?

[joerick]

Could you post a link to the project code that you're building?

[nschloe]

I made an MWE here.

The data is uploaded on PyPi; see the size of the wheels increasing.

[henryiii]

Going to guess nuitka doesn't handle caching correctly and is collecting the outputs cached by initial runs. It should cache based on Python version, os, etc - everything that goes into a wheel.

To fix it you could add a pre-build step that deletes the cache, though you'd need to figure out where they are caching the outputs.

[henryiii]

"Temporarily fix it", I mean, nuitka really should fix it. :)

[nschloe]

I'll see what I can do. Thanks for the advice!