Convert to poetry

[mgdaily]

• Uses poetry for dependency management
• Constrain to python>=3.8
• Update GH workflows
• Update README

Thanks for the help, Jesus! (can't add him til he accepts the org invite)

[jnation3406]

Looks good, just one question about the pypi deploy

[jnation3406]

The setup.py deploy to pypi used the tagged version, but now you are explicitly setting the version here. Does this mean we have to be careful to keep this version in sync with the tagged version so it is deployed to pypi as the correct version now?

[mgdaily]

Thought about this too - maybe we can do something like this?

We'd have a dummy placeholder in the pyproject.toml, but then on tag we'd update it when pushing to PyPI. The downside of this is when the user installs it locally from the git repo, it would show them as having the dummy version installed. But realistically, most users are going to be installing it from PyPI

[jashan-lco]

IMO, it's semantically more correct to keep the version in pyproject.toml file and then commit & tag. Tags should be thought of as pointers to the complete source code w/ the versions included. To help avoid synchronization errors, I would create a manually trigger-able workflow that does that for us, e.g. sourcing it from poetry version -s.

[jashan-lco]

Since you were asking about conventions...something I've been thinking about is how to make sure we're using the same version of poetry here, locally and in the Dockerfile. I've been creating a poetry-requirements.txt with poetry>1,<2 and then pip install -r poetry-requirements.txt everywhere so that you don't have to repeat the version. Maybe something to consider for the other repos.