http-ece 1.2.1 is pure Python and configured for a universal wheel, but PyPI contains only the 8.8 KB source archive. Every downstream installation therefore has to invoke a build backend.
release.sh currently builds and uploads only an sdist. Could the next release build and upload both an sdist and a wheel, and include the repository-root MIT LICENSE in the Python distributions? The approved pyproject migration in #86 deletes setup.py without updating release.sh, so that script will also need to switch to the new build entry point.
http-ece 1.2.1 is pure Python and configured for a universal wheel, but PyPI contains only the 8.8 KB source archive. Every downstream installation therefore has to invoke a build backend.
release.sh currently builds and uploads only an sdist. Could the next release build and upload both an sdist and a wheel, and include the repository-root MIT LICENSE in the Python distributions? The approved pyproject migration in #86 deletes setup.py without updating release.sh, so that script will also need to switch to the new build entry point.