Can you publish a wheel for armv7l?

Older RasPi’s, various embedded boards, OpenWRT routers are the things that could be supported, in addition to the aarch64 port already present

Feel free to ignore if unhelpful, but I was wondering why a custom make_wheels.py script is being used rather than a standard setup.py script (or perhaps setup.cfg or pyproject.toml) with setuptools? I imagine there's a good reason that I'm not seeing :)

Perhaps worth pointing out that https://github.com/pypa/wheel#wheel states:

It should be noted that wheel is not intended to be used as a library, and as such there is no stable, public API.

The reason I was wondering is I was thinking it might be helpful to give the ziglang package a zig entrypoint, i.e. when installing into a venv with pip install ziglang you would get a venv/bin/zig executable, which would be on PATH when the venv was active. Definitely not necessary for the intended use-case, and not obviously desirable in general, but was just a thought that this could be used as a slight abuse of PyPI/pip just for installing zig!

On Alpine linux running:

pip install 'ziglang==0.10.0'

Fails with:

ERROR: Could not find a version that satisfies the requirement ziglang==0.10.0 (from versions: 0.0.0)
ERROR: No matching distribution found for ziglang==0.10.0

I think this is because the publishing script only releases manylinux wheels and not musllinux wheels https://github.com/ziglang/zig-pypi/blob/8d37e955e3af0c0d88851e8283081b89b074e3bc/make_wheels.py#L115-L122

Since the linux- binaries published on the zig website are statically linked I think changing

    'linux-x86_64':   'manylinux_2_12_x86_64.manylinux2010_x86_64',

to

    'linux-x86_64':   'manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64',

to the publishing script should work.

I tested this out locally by downloading ziglang-0.10.0-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.whl and renaming it to ziglang-0.10.0-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl and then running python3 -m ziglang worked fine.

Publishing this wheel means running pip install maturin[zig] on Alpine linux will work as well.

Using an os.exec* function, when available (Unix, Windows) will replace the Python wrapper process, rather than keeping it around until zig has finished. This saves memory and makes processes easier to debug.

You should be able to change:

sys.exit(subprocess.call([
    os.path.join(os.path.dirname(__file__), "{entry_name}"),
    *sys.argv[1:]
]))

to something like:

path = os.path.join(os.path.dirname(__file__), "{entry_name}")
os.execvp("zig", path, *sys.argv[1:])