Migrate Pipenv to Poetry for Package and Environment Support

[joshmgrant]

Currently, this project uses Pipenv to manage pip and virtual environments together. While Pipenv has some benefits, the project has largely been sunsetted. This suggests three options:

1. Migrate to using Poetry as a replacement for Pipenv. Poetry is gaining popularity as a package and environment handling tool with several benefits and wide adoption so far. Poetry has a good developer experience and allows folks to avoid setting up and managing Python versions and virtual environments manually.
2. Use a conventional requirements.txt file without any environment handling. This is the conventional way for Python projects to handle environments, but can lead to confusion with handling virtual environments and changing Python versions.
3. Keep using Pipenv and don't change anything.

This is a smallish Python project that doesn't require any packages to be published nor does it have regular "builds" of an application.

Personally, I'm in favour of 1, but I'd like to see what other folks think!

[joshmgrant]

Hi @johnorrsauce and StuMinch, let me know if you'd like me to open a PR for this issue. Or not, it's up to you :)

[StuMinch]

Hi @johnorrsauce and StuMinch, let me know if you'd like me to open a PR for this issue. Or not, it's up to you :)

I have no objections to option 1 :-) I'm not familiar with Poetry, but read it is like npm for Python and continues to grow in popularity.