Publish version 0.1.0a0

[davidorme]

Description

This PR is to merge the current develop into the release branch main so that we can then publish the current code onto PyPI and get the project name fixed in PyPI. As part of this process, I'll also run a test publish to TestPyPI.

This isn't a particular target hit or goal achieved, but it is worth making sure we have everything set up and have an official PyPI page for the upcoming paper submission.

Type of change

• New feature (non-breaking change which adds functionality)
• Optimization (back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)

Key checklist

• Make sure you've run the pre-commit checks: $ pre-commit run -a
• All tests pass: $ poetry run pytest

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added that prove fix is effective or that feature works

[dalonsoa]

Looks good to me. I've just made a couple of suggestions to move files from one place to another.

To automate the pubisling to PyPI when you create a new release, I'd suggest you follow something similar to what we implemented in this other project: https://github.com/EnergySystemsModellingLab/MUSE_OS/blob/develop/.github/workflows/publish.yml
You will need to setup accounts in PyPI and TestPyPI firs, obviously.

[davidorme]

@dalonsoa The PR template is in a recognised location, but I agree it's neater in .github. It seems dependabot.yml must be in .github though, so I botched a PR two years ago 😄.

Having an automatic PyPI setup would be good - I might just do this one manually to get it released and then we can revisit that for the next release?

[dalonsoa]

Sounds good!

[vgro]

I have nothing to add :-)

[davidorme]

Just pulling in the progress update from #403.