pythonpython-websockets/websockets #1300Not a task: already works

[Proposal] Publish an architecture-independent `websockets-11.0-none-any.whl`

envgap__python-websockets__websockets-1300

Original GitHub issue ↗Dated source checkout ↗Opened 2023-02-22

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 6dcac04c10c61dde9aa5be0374965c31f16e77f4
Manifest: setup.py
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

python-websockets/websockets #1300 · read the original issue

Dear community

I hope this finds you well 😄



I currently write a Python application on an ARMv7-based IoT computer running Linux. As the `websockets` package is only providing wheels for major architectures and platforms (such ARM64, x86-x64, etc.), it would be really great if you could provide a `websockets-11.0-py37.py38.py39.py310.py311-none-any.whl` on PyPi as well (without the `speedups.c` extension).



I currently build and use the pure Python wheel on my own. Nevertheless it would be great for other people, to have support for some more exotic or industrial platforms and not have to take the same steps I had to take. As websockets are more and more common in these fields, I also see quite some adoption.



Tell me what you think 😉



Best regards

Markus

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]