messense

FYI: a related upstream issue: https://github.com/pypa/setuptools/issues/1272

Although we can not extend `setup.cfg`, we can certainly extend `pyproject.toml` to add a `[tool.setuptools-rust]` section, for example ```toml [[tool.setuptools-rust.rust-extensions]] target = "example" binding = "pyo3" ``` Then we can...

Right, but it should work after merging https://github.com/pyca/cryptography/pull/7164

Or we can add a `[tool.setuptools-rust.extra-setup-args]` that can add arbitrary arguments to the generated `setup.py`. ```toml [tool.setuptools-rust.extra-setup-args] cffi_modules = ["src/_cffi_src/build_openssl.py:ffi"] ```

According to https://packaging.python.org/guides/distributing-packages-using-setuptools/#wheels , you should only use `universal = 1` if your project does not have any C extensions and supports Python 2 and 3. I'm not sure about...

The benefits of universal wheel is that it can run on both Python 2 and 3. Since Python 2 support is no more, if you only needs to support Python...

I've made a tool for this today: https://github.com/messense/auditwheel-symbols ```bash pip install auditwheel-symbols ❯ auditwheel-symbols --manylinux 2014 ~/Downloads/rjieba-0.1.5-cp36-abi3-manylinux2010_x86_64.whl rjieba/rjieba.abi3.so is manylinux2014 compliant. ❯ auditwheel-symbols --manylinux 1 ~/Downloads/rjieba-0.1.5-cp36-abi3-manylinux2010_x86_64.whl rjieba/rjieba.abi3.so is not manylinux1...

I've built https://github.com/messense/manylinux-cross , it's been used in https://github.com/messense/maturin-action , although it only has very old GCC 4.8.5 and 6.5.0.

I'm fine with manylinux_2_24 EOL. I mostly work on [manylinux cross compiling docker images](https://github.com/messense/manylinux-cross), they are stuck on old GCC toolchain because of lacking devtoolset based cross compilers, but since...

I've updated the code to grpcio 0.4.0, the bug still exists but seems harder to reproduce.