publish wheels

[dimbleby]

Description

we did this already at #1187, but I see that nevertheless there is no wheel at https://pypi.org/project/juju/3.6.1.2/#files

did something go wrong?

Urgency

Casually reporting

Python-libjuju version

3.6.1.2

Juju version

n/a

Reproduce / Test

-

[dimaqq]

I'm happy to push the wheel.

@dimbleby may I ask why a source wheel is needed when an sdist is available, both now and last year?

[dimbleby]

All installation is from wheel. So if you publish only a source distribution then every user must build the wheel themselves at install time.

This is slower - and can even go wrong. In recent weeks both wheel and setuptools have published breaking changes so that some previously functional source distributions became unusable.

Better for package maintainers to build the wheel once and for all.

[dimaqq]

Those are valid arguments.
This library, however, is (mostly) in security and critical bug fix maintenance mode now.
We recommend that users switch to https://pypi.org/project/jubilant/

[dimbleby]

I would view that as all the more reason to publish a wheel!

If it's likely that you won't be making updates - then whatever you publish now might need to be valid more or less forever. As above, source distributions are much more vulnerable to the possibility of setuptools etc breaking something, a wheel protects you and your users against such things.

[dimaqq]

You may be delighted to know that the most recent patch release comes with wheels.

Well, with one wheel.

https://pypi.org/project/juju/#files