build and publish a wheel
envgap__apple__foundationdb-12665
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
c62bb6bf3817da2a3659459b4bcf44528aae65c2- Manifest
bindings/python/CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
apple/foundationdb #12665 · read the original issue
I notice that this package publishes [only source distributions](https://pypi.org/project/foundationdb/#files), so that every user has to build the wheel themselves. Better for package owners to build and publish wheels once and for all. I see that #12082 claimed > wheel files are not accepted anymore I do not know what was misunderstood here, but this is certainly not correct. [Wheels](https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#wheels) are the preferred distribution mechanism, even for pure python files. In python, all package installation is from wheel. By publishing only a source distribution you force every user first to build the wheel and then install it. Publishing the wheel so that users can install it directly is better for lots of reasons: it is faster, it is one less thing that can go wrong, it avoids having to trust arbitrary code execution at install time, etc @xis19
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]