GHC 2019-12-21

2019-12-21 07:11:21, https://git.io/JedEz in jarun/imgp

Of course, but if you find yourself maintaining a dozen packages one day with a more rapid release cycle this file and forget (especially for pure Python packages) would come in handy ;)

2019-12-21 07:06:09, https://git.io/JedEg in jarun/imgp

Forgot to mention: automatically publishing to PyPI with GitHub Actions is pretty nice. https://github.com/pypa/gh-action-pypi-publish

PyPA has an easy-to-follow guide: https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Here's a recent example in production from yours truly: https://github.com/zmwangx/miller-rabin/blob/master/.github/workflows/build-and-publish-distributions.yml (Way more complicated than what you need, since I'm building a statically-linked C extension there, whereas yours is just pure Python.)

2019-12-21 06:55:16, https://git.io/Jed0X in jarun/imgp

Btw I recommend using 2FA and project-scoped API tokens with PyPI (support added earlier this year).

https://pyfound.blogspot.com/2019/07/pypi-now-supports-uploading-via-api.html

2019-12-21 06:52:54, https://git.io/Jed01 in jarun/imgp

```command
pip3 install -U wheel twine
python3 setup.py sdist
python3 setup.py bdist_wheel
# Optionally PGP-sign dist/imgp/$version{.tar.gz,-py3-none-any.whl}, producing .sig or .asc signatures which could also be uploaded, but mostly pointless.
twine upload dist/imgp-$version{.tar.gz,-py3-none-any.whl}
```

2019-12-21 06:49:03, https://git.io/Jed0M in jarun/ddgr

In addition to `MANIFEST.in`, I also recommend adding the `license_file` key to `setuptools.setup`.