KohakuBlueleaf
publish a wheel
I notice that this package publishes only source distributions, so that every user has to build the wheel themselves. Better for package owners to build and publish wheels once and for all.
I did not find a workflow in this repository for publishing or I would have submitted a pull request. If you are doing this manually a typical workflow would be something like
python -m pip install build twine
python -m build
twine upload dist/*
I use build -s since I don't see any reason to publish a wheel for pure py project.
but if you think it is BETTER, I would do that
Is there any specific reason that "wheel for pure py project" is also considered "better"?
In python, installation is always from a wheel. So if you distribute only a source package then every user must first build the wheel, and only then can install it.
That's slower - and can sometimes go wrong. In recent weeks, both setuptools and wheel have released breaking changes which made previously usable source distributions fail to build.
Better for maintainers to build and publish wheels: making installs faster, and safer against such breakages.
@dimbleby Thx for your explanation and I plan to update ALL my project to use wheel now I have some internal workflow and templates so it may take a little time to achieve it.
You should see wheel of LyCORIS soon within this mo