[PATCH] scripts: Publish both source and wheel

[Jan Kiszka]

From: David Hotham <david....@blueyonder.co.uk>

In python, all package installation is from wheel. So if maintainers do
not publish wheels, then every user install must start by building a
wheel.

That has a few minor disadvantages: it is slower, it is a thing that can
go wrong, security-conscious users will want to avoid code execution at
install time...

Best practice is to publish both sdist and wheel.

Signed-off-by: David Hotham <david....@blueyonder.co.uk>
Signed-off-by: Jan Kiszka <jan.k...@siemens.com>
---

See also https://github.com/siemens/kas/pull/172

scripts/release.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/release.sh b/scripts/release.sh
index 9e11099..8eabcfd 100755
--- a/scripts/release.sh
+++ b/scripts/release.sh
@@ -41,8 +41,8 @@ git commit -m "Release $NEW_VERSION"
git tag -s -m "Release $NEW_VERSION" "$NEW_VERSION"
git push --follow-tags

-python3 -m build --sdist
-twine upload -s -r pypi "dist/kas-$NEW_VERSION.tar.gz"
+python3 -m build
+twine upload -s -r pypi "dist/{kas-$NEW_VERSION.tar.gz,kas-$NEW_VERSION-py3-none-any.whl}"

authors=$(git shortlog -s "$OLD_VERSION".."$NEW_VERSION" | cut -c8- | paste -s -d, - | sed -e 's/,/, /g')
highlights=$(sed -e "/$OLD_VERSION$/,\$d" CHANGELOG.md)
--
2.47.3