build and publish wheel

[dimbleby]

No description provided.

[zeroSteiner]

Is there some kind of advantage to the wheel over the source distribution for this package? I'm not familiar with this build package that's used now so I'll need to look into it.

[dimbleby]

the way packaging works in python is that every installation is from a wheel. By publishing only a source distribution you are requiring all of your users to build the wheel: which is slower, and has some non-zero chance of going wrong.

Better for package owners to build and publish wheels once and for all

Direct invocation of setup.py is considered deprecated, the build package is a commonly recommended replacement eg https://packaging.python.org/en/latest/discussions/setup-py-deprecated/

[zeroSteiner]

I appreciate your interest in rule-engine and bringing this to my attention. However, I've decided that I will not be merging this PR.

I actually generate the ci.yml file you edited from a template I have that I share with my other projects. Until there's a need for me to adjust how I package and release my builds, I'd prefer to keep them all uniform so that I can more easily troubleshoot and maintain them. I'm also hesitant to add another dependency when there's not a clear issue that it solves.

[dimbleby]

To be honest my interest is more in the broader ecosystem then in this project specifically.

Per the advice that I linked

• your current use of setup.py is deprecated (and will eventually break)
• it is just better to publish wheels than not

So I hope that at some point you will update your template to Do The Right Thing!

But it would be a stretch to call it urgent. All the best either way.