✨ Migrate package installation to pyproject.toml (PEP 621)

[Ambro17]

Intro

Based on #52 and the suggestion of the andrew-d to inspire the solution on starlette's setup and the apparent inactivity of the PR, i port the installation of the lib to use the new packaging standards of using pyproject.toml and starlette's style. I modified the invoke tasks so you can release a new version with the same setup as before

Solution

First install dev dependencies with pip install .[dev]. Editable installs work from pip==21.3 so an editable install to iterate on refactors will also work. This is safer though because it avoid running tests with local changes and publishing another, not-tested version.
So with hatch how do we handle packaging tasks?

Build distribution artifacts (source and build)

hatch build

This will save a source and wheel artifact into the default folder dist/

Upload distribution artifacts

hatch publish

Run Tests

inv test

Bump the library version

inv bump minor/major/patch

Could be also replaced by https://hatch.pypa.io/latest/version/#updating if you prefer the hatch native way. If you do not, the above still works

Deploy a new version, enforcing a test run

inv deploy

It will interactively ask for your pypi creds

Let me know if you only want to offer a wheel artifacts or if there is any incompatibility with a platform. My educated guess is we won't since we're not using any platform-specific magic on the lib but i'm not the author so feel free to correct me

All tests pass using python3.7.15 virtualenv. I can try with the 3.8, 3.9, 3.10 and 3.11 too if you want. I noticed the invoke task api changed so i updated the tasks accordingly. Please tell me if you prefer to pin an older version of invoke to avoid this changes

[Ambro17]

@andrew-d can you review when you have time? Thanks!

[Ambro17]

Adressed all comments. Can i have another look @Kludex @ofek? Thanks in advance

[Kludex]

cc @tomchristie

[ofek]

🥇

[tomchristie]

I'm happy to facilitate a release here, if that's what folks would like.

[Kludex]

I'm happy to facilitate a release here, if that's what folks would like.

Thanks 👍

[tomchristie]

Do we need anything else before rolling a new release here?

[Kludex]

We need an analogous workflow to encode projects to release the package via pipeline.

[Ambro17]

Thank you for merging 🙂

I'd be happy to contribute with another PR that sets up the release pipeline in case you're interested

[Kludex]

We are. 👍