Some comments about Packaging and Versioning

[AKuederle]

Great job publisheing the package on Pypi!

Here a couple of suggestions to further improve packaging and distribution:

• [x] Your package should have an internal version identifier (usually a version const in the init) that corresponds to the package version, so that users can check which version they have installed
• [x] You should associate each Pypi release with a git tag (and push the tag to Github) to make sure that people can browse the code of exactly the version they are currently running (e.g. when reporting bugs)
• [x] Optionally, you can create a Github release for every version
• [x] Optionally, you can streamline the process, by using Github actions to automatically publish on release or on tag
• [x] You should consider adding a changelog. Otherwise, new versions and their impact are meaningless to users.

[Aminsinichi]

• [x] The first suggestion was about including the version to init. Apologies, I accidentally turned this into a new issue and then removed it. Your suggestion has been incorporated related commit.
• [X] Many thanks for these useful suggestions. I have now added a GitHub Action, which automates the process of publishing on PyPI, and is triggered by pushing the version as a tag, which hopefully will resolve the issue. Related commit1; Related commit2
• [X] Added a template changelog, and will update this with every newer version from now on Related commit.