Henry Schreiner
Henry Schreiner
I'd highly recommend using cibuildwheel. There are several other concerns; for example, you don't want to use the GitHub Actions compiled Python or brew's compiled Python, as those don't target...
I would recommend all projects have a `pyproject.toml`, regardless of if they have a `setup.py`, it's not a replacement, even if it can be in some cases. It's a file...
See https://cibuildwheel.pypa.io/en/stable/setup/ and https://learn.scientific-python.org/development/guides/gha-wheels/ for some info.
Last I heard this was still experimental. Also, setting `tool.distutils.bdist_wheel.universal = true`, which declares a wheel can be run with Python 2 and 3, in a way that is not...
@abravalheri is this something that can be shown in docs yet?
Quick workaround if you need it - since it's an "assert", you could disable assertions by running Python in optimized mode (`-O` or `PYTHONOPTIMIZE=TRUE`).
You cannot compute what a wheel tag will be in advance, because that depends on the backend. A setuptools / wheel wheel will depend on what's in the setup.py -...
The two can coexist fairly nicely, that is, setup.py/setup.cfg/pyproject.toml/MANIFEST.in at the top and "python/aghast" instead of "src/aghast", then the rest of the parts can sit in the top namespace, since...
We could leave the directory name as python, we just would need to move the packaging tools (`setup.*` etc) to the top level.
See https://scikit-hep.org/developer/packaging - just change `src` to `python` when reading it.