Convert the project from setuptools -> poetry

[tarkatronic]

This sets us up with Poetry instead of setuptools. This way we actually have a legit package manager, dev environment manager, deterministic builds, etc etc etc.

Steps for this to be considered complete:

• Move setup.py metadata into pyproject.toml
• Update sphinx to pull version from pyproject.toml
• Update tox to work with/use Poetry
• Update Dockerfile to work with/use Poetry
• Update build script(s) to work with/use Poetry
• Update Travis config to use Poetry
• Update contributing docs to guide users on using Poetry
• Deprecate setup.cfg
  • Move config to pyproject.toml where possible
  • Otherwise, move to tool-specific config file
  • Bonus: Bring other config files into pyproject.coml where possible

I'm pretty sure that's all that's left... I will add any other things here which pop up.

[codecov]

Codecov Report

Merging #52 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   81.00%   81.00%           
=======================================
  Files           5        5           
  Lines         416      416           
  Branches       88       88           
=======================================
  Hits          337      337           
  Misses         60       60           
  Partials       19       19           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce4258e...d2bf668. Read the comment docs.

[tarkatronic]

@kquerna I would love to get your input on the updates to the contributing docs here. 😄

[bosatsu]

Curious why we are going this route, rather than just using poetry install and poetry build?

[tarkatronic]

The idea here is that we ship a final image with none of the build artifacts; only the finally installed product. If you notice, poetry is not installed into the venv, and so doesn't actually get copied over to the final image. Same with the -dev packages installed on line 12. The main goal here is to provide as compact and clean an image as we can.

So with all of that in mind, the easiest way to get Poetry to use the Python interpreter in the venv, is to do this export and pip install.

Of course, all this is adapted from a number of examples I've found online. So I'd be happy if somebody is able to help build a better way!

[bosatsu]

Consider including a link on how to install poetry?
https://python-poetry.org/docs/#installation

[tarkatronic]

Like this? 😄