Preparing migration to Poetry

[femueller]

Part of: #121

Done using Dephell:

dephell deps convert --from=Pipfile --to-format=poetry --to-path=pyproject.toml

What's missing:

• PyPI releases via Poetry
• Modify Dockerfile to use Poetry
• Modify Makefile to use Poetry

[femueller]

Once the PyPI release process works via Poetry, we also don't need to generate a requirements.txt anymore.

[femueller]

I went with this GitHub Action as it seems to be actively maintained and the most used for poetry publish. Still need to verify if it works as expected.

[femueller]

@markusressel I haven't used the Dockerfile yet. Is it from your perspective simple as that replacing pipenv with poetry in the Dockerfile?

[markusressel]

No. Take a look at this one: https://github.com/ekeih/alerticular/blob/main/Dockerfile

[markusressel]

The referenced Dockerfile uses Alpine as a base, which has its downsides, see: https://pythonspeed.com/articles/alpine-docker-python/

For a version based on buster, have a look at this one:
https://github.com/markusressel/openhasp-config-manager/blob/main/Dockerfile

The mentioned file is also used for a CLI tool, so it should be more fitting to python-n26 than the one from alerticular.