Having trouble doing native builds on macOS 11 x86_64 runner.

[cheofusi]

Hi everyone,

I was hoping this simple workflow gets me Windows , Linux & MacOS wheels. It works for all except the macOS runner, failing with a OSError: [Errno 66] Directory not empty. Seems to me like an issue with setuptools on the macOS.

Has anyone come across something similar ? Any thoughts would be greatly appreciated.

[Czaki]

I do not understand why but it fails with the building a wheel for cffi that provides a wheel for this python version.

[cheofusi]

Thank you both... I'll ditch setup.py as soon as I can

[henryiii]

You can't ditch setup.py, it's an extra file - you need setup.py and pyproject.toml. Your pyproject.toml file tells Python to read the setup.py and what dependencies it needs when it runs the setup.py. You can only remove this one line by adding that to pyproject.toml. (though you can technically remove quite a few of them with the new pyproject.toml support in setuptools 61+ if you want; I think you are only truly stuck with the cffi_modules one for now).

At least, not yet, but this got funded: https://iscinumpy.dev/post/scikit-build-proposal/, so I'm going to be working on better binary build options :)

[cheofusi]

Godspeed on scikit-build. Could one get away with pyproject.toml + setup.cfg + build ?

[henryiii]

Normally I'd say no, you can't make an Extension via setup.cfg or pyproject.toml. However, given that cffi has a setuptools plugin that just requires a configuration value, I'm not so sure; it might be supported either in Setuptools' setup.cfg mode or pyproject.toml config mode.

[henryiii]

FYI, pipx run hatch new --init will auto-convert your setup.py into a hatchling based pyproject.toml, then you could just move back to setuptools and re-add this config value to [tool.setuptools], that would be the quickest way to check setuptools 61+'s config mode.