Publish on PyPI

[mikegerber]

• [x] Upload to PyPI
• [x] Review metadata on PyPI
• [x] Remove the warning about not being on PyPI...
• [x] Update again
• [x] Consider releasing via GitHub Actions
  • https://github.com/marketplace/actions/pypi-publish
  • [x] Only do this if build and tests are ok
  • [x] Share build + test between GHA jobs
  • [-] Make workflow reusable - Could use the same workflow for dinglehopper
  • [x] The only thing specific is the PyPI URL

[mikegerber]

0.0.4 is now available on PyPI for testing → https://pypi.org/project/setuptools-ocrd/

👀 @kba

[mikegerber]

Metadata looks ok now on PyPI. I removed the extra license field from pyproject.toml as https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata-license says, that the classifiers should be used instead. The LICENSE file stays, just in case.

[mikegerber]

Now publishing to PyPI with a GitHub Action. This works really really well and elegantly (e.g. using trusted publishing for the credentials).

[mikegerber]

More info on Trusted publishing (= GitHub using OIDC to authenticate with PyPI + authorizing GitHub Actions to publish a certain package "from" a specific GitHub repo):

https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/

[mikegerber]

Making the workflow reusable for e.g. dinglehopper is blocked by external issues, I opened #9 for this.

[mikegerber]

GitHub and PyPI releases are now created by the same GH workflow (release.yml) and share building and testing.

Testing is just a dummy test, see #6 in the future.