Build via 'python -m build'

[hugovk]

This should fix #91.

❯ python -m build .
* Creating virtualenv isolated environment...
* Installing packages in isolated environment... (flit_core>=3.2,<4)
* Getting build dependencies for sdist...
* Building sdist...
* Building wheel from sdist
* Creating virtualenv isolated environment...
* Installing packages in isolated environment... (flit_core>=3.2,<4)
* Getting build dependencies for wheel...
* Building wheel...
Successfully built cherry_picker-2.2.0.tar.gz and cherry_picker-2.2.0-py3-none-any.whl

❯ ls dist
cherry_picker-2.2.0-py3-none-any.whl cherry_picker-2.2.0.tar.gz

[Mariatta]

Can we use flit publish?

[hugovk]

I've never used flit as a command, but the docs say of flit publish:

Build a wheel and an sdist (tarball) from the package, and upload them to PyPI or another repository.

https://flit.pypa.io/en/stable/cmdline.html#flit-publish

So it could potentially replace both of these lines (and update the pip install):

          python -m build .
          twine upload dist/*

But I'll look into trusted publishers as a longer term fix.

[Mariatta]

I think let's just get this set up with Trusted Publishers and the GItHub Actions that you mentioned.

[hugovk]

Superseded by Trusted Publishing 🚀

#94